Retrieve matches for a saved Feedbin search as entry IDs, or include full entries when include_entries is true. Use pagination for additional results.
Get saved search matches (entry ids, or entries if include_entries=true).
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| search_id | Yes | ||
| include_entries | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It usefully discloses that the default result is entry IDs and that include_entries=true returns full entries, but it omits pagination behavior via the page parameter, authentication requirements, and error behavior for invalid search IDs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no filler. The parenthetical efficiently conveys the conditional output behavior, though the structure is minimal.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a three-parameter getter with no annotations and no output schema, the description covers the core return variation but leaves pagination and error/auth context undocumented. It is minimally viable but incomplete for an agent needing to invoke it correctly in all cases.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must document all three parameters. It explains the effect of include_entries and implies the role of search_id, but never mentions the page parameter or its pagination semantics, leaving a clear gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Get') and resource ('saved search matches'), and clarifies the output variation via include_entries. It does not explicitly distinguish itself from sibling tools such as feedbin_list_saved_searches or feedbin_list_entries, but the resource is distinct enough for an agent to identify the operation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives like feedbin_list_saved_searches (to list saved searches) or feedbin_list_entries (to browse entries). The only conditional mentioned concerns output shape, not tool selection or context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.