list_recipes_timeline_eventsRetrieve a paginated list of recipe timeline events with filtering, sorting, and pagination options to track recipe changes and activity.
Get All
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| orderBy | No | ||
| perPage | No | ||
| queryFilter | No | ||
| orderDirection | No | ||
| paginationSeed | No | ||
| accept-language | No | ||
| orderByNullPosition | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v3.20.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure, but 'Get All' provides none. It is actively misleading because the schema includes page, perPage, and paginationSeed, implying a paginated list rather than retrieving all records at once.
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?
Two words is concise, but this is underspecification rather than effective brevity. There is no sentence structure, no front-loaded key information, and no content that helps an agent use the tool.
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?
Given eight optional pagination/filter parameters, CRUD siblings, and no annotations, this description is completely inadequate. An agent cannot determine the tool's scope, return behavior, or even the resource being listed.
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% and the description provides no parameter information. None of the eight pagination, ordering, filtering, or language parameters are explained, so the description does nothing to compensate for the schema 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 'Get All' is generic and does not name the resource or action domain. It does not distinguish this tool from siblings like get_recipes_timeline_events_by_item or list_recipes, and it is close to a tautological fragment rather than a real purpose statement.
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. The description does not mention filtering, pagination, or the difference between listing all events and getting a single item, so an agent has no context for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.