Skip to content

[MCP] Add safety annotations to search tool - #43

Merged
vm-serpapi merged 1 commit into
serpapi:mainfrom
louzt:feat/safety-annotations
Jun 9, 2026
Merged

vm-serpapi merged 1 commit into
serpapi:mainfrom
louzt:feat/safety-annotations

Conversation

@louzt

@louzt louzt commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Implementation of safety annotations for the SerpApi search tool.

Closes #39

@adarshdigievo
adarshdigievo self-requested a review June 9, 2026 13:22
@adarshdigievo

Copy link
Copy Markdown
Member

@louzt Thanks for working on this.

All changes look good on my end.

Answer to your queries:

Should we also annotate the engines_index resource? Currently it
doesn't have a ResourceAnnotations block. Could be a follow-up.

This will be a nice addition too.

Is there a preference for idempotentHint=True given the 1h cache?
Current draft uses False to be conservative; happy to flip if the
maintainer wants.

We can keep it as-is. As per the latest MCP spec, idempotentHint property is meaningful only when readOnlyHint == false

@adarshdigievo

Copy link
Copy Markdown
Member

Also, closes #37 once merged

@vm-serpapi vm-serpapi left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks for contributing @louzt

@vm-serpapi
vm-serpapi merged commit a18058b into serpapi:main Jun 9, 2026
1 check passed
louzt added a commit to louzt/serpapi-mcp that referenced this pull request Jun 10, 2026
Follow-up to serpapi#43: annotate the serpapi://engines discovery resource so
clients can classify it as low-priority, assistant-only metadata.

Per the MCP 2025-11-25 spec, Resource.annotations only supports
audience and priority (readOnlyHint/destructiveHint/idempotentHint/
openWorldHint are tool-only and intentionally omitted).
louzt added a commit to louzt/serpapi-mcp that referenced this pull request Jun 10, 2026
Follow-up to serpapi#43: annotate the serpapi://engines discovery resource so
clients can classify it as low-priority, assistant-only metadata.

Per the MCP 2025-11-25 spec, Resource.annotations only supports
audience and priority (readOnlyHint/destructiveHint/idempotentHint/
openWorldHint are tool-only and intentionally omitted).
vm-serpapi pushed a commit that referenced this pull request Jun 10, 2026
Follow-up to #43: annotate the serpapi://engines discovery resource so
clients can classify it as low-priority, assistant-only metadata.

Per the MCP 2025-11-25 spec, Resource.annotations only supports
audience and priority (readOnlyHint/destructiveHint/idempotentHint/
openWorldHint are tool-only and intentionally omitted).
louzt added a commit to louzt/serpapi-mcp that referenced this pull request Jul 27, 2026
Co-authored-by: Lou <opensource@loust.pro>
louzt added a commit to louzt/serpapi-mcp that referenced this pull request Jul 27, 2026
Follow-up to serpapi#43: annotate the serpapi://engines discovery resource so
clients can classify it as low-priority, assistant-only metadata.

Per the MCP 2025-11-25 spec, Resource.annotations only supports
audience and priority (readOnlyHint/destructiveHint/idempotentHint/
openWorldHint are tool-only and intentionally omitted).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add MCP safety annotations to search tool

3 participants