List all timelines for a specific campaign using its ID. Retrieve an overview of your campaign's chronological events to manage worldbuilding history.
List timelines
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| campaignId | Yes |
Changes observed during successful MCP inspections.
v2.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears the full burden of behavioral disclosure. 'List' implies a read-only operation, but the description does not mention pagination behavior, campaign scoping, permissions, or what response shape to expect.
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 under-specification, not effective conciseness. A useful description of a list operation with required and optional parameters should include more operational context.
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?
With no annotations, no output schema, incomplete parameter documentation, and a broad sibling set, this description is far too thin. It does not explain what a timeline is, how campaignId filters results, or how page behaves.
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 compensate by explaining the two parameters. It does not mention campaignId or page at all, leaving the agent to guess that campaignId is required and how pagination works.
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 'List timelines' is a tautology that simply restates the tool name. It names a verb and resource but adds no scope or differentiation from siblings like get_timeline or list_events.
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 about when to use this tool versus alternatives such as get_timeline, create_timeline, or list_campaigns. An agent must infer the intended use entirely from the name and schema.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.