Fetch CTV News stories from its public news sitemap, returning items from the past 24 hours with headlines, publication times, and lead images.
Get CTV News top stories. Returns the newest CTV News stories (about the last 24 hours, newest first) from its public news sitemap, each with headline, publication time and lead image.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the time window (last 24 hours), ordering (newest first), source (public news sitemap), and return fields (headline, publication time, lead image). This is a clear, non-mutating read operation, and the description does not contradict any annotations.
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 concise, containing only two sentences that provide essential information: what the tool does, its source, the time window, ordering, and return fields. It is front-loaded with the primary purpose, making it easy for an agent to quickly parse.
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 zero-parameter tool with no output schema, the description is complete: it specifies the source, time range, ordering, and typical output fields. Given the simplicity of the tool, nothing essential is missing.
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?
With zero parameters, the description correctly notes that no input is required. Since there are no parameters, the description's role in parameter semantics is minimal, but it effectively communicates that the tool needs no configuration. The baseline for zero parameters is 4, which is appropriate.
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 clearly states the tool fetches CTV News top stories from a public news sitemap, returning the newest ones (last 24 hours, newest first) with headline, publication time, and lead image. It distinguishes from sibling tools like ctvnews_headlines and ctvnews_sections by specifying the sitemap-based, time-filtered behavior.
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?
The description implies usage (get top stories for news updates) but does not explicitly state when to use this over siblings like ctvnews_headlines or ctvnews_news. However, the time frame and sitemap source give enough context that an agent could infer the appropriate use case.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.