Fetch CBS News section headlines through Crawlora MCP and return RSS-based stories as structured JSON for news monitoring or feeds.
Get CBS News section headlines. Returns fresh headlines from one public CBS News RSS section.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | CBS News RSS section slug |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden of behavioral disclosure. It states headlines are 'fresh' and from a public RSS section, but does not explain response format, pagination, error behavior, or any rate limits. For a simple read tool this is minimal but not egregiously lacking, though it offers little beyond the basic action.
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 two sentences and front-loads the core purpose. It is concise with no redundancy, but it omits potentially useful details like the response shape. It is efficient but arguably too sparse for a complete tool definition.
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 only one parameter and no output schema, the description provides the essential action and mentions the source is public and fresh. However, it does not describe what the returned headlines look like (e.g., titles, URLs, timestamps) or any limitations. For a simple tool it is acceptable but not fully complete; an agent might still be uncertain about the exact return structure.
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?
The schema already documents the 'section' parameter with an enum and description, achieving 100% schema description coverage. The description adds that it selects a section from a public RSS feed, which slightly extends the meaning but does not elaborate on the parameter format or any special values. Baseline 3 is appropriate since the schema does the heavy lifting.
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 retrieves CBS News section headlines, a specific verb+resource. It also mentions the source is a public RSS section, which adds context. However, it does not differentiate from sibling tools like cbsnews_news or cbsnews_sections, though the intent is fairly obvious from the name.
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?
No guidance is provided on when to use this tool versus alternatives. It does not mention any exclusions or scenarios where a different tool (e.g., cbsnews_news for full articles) would be more appropriate. The description only states what it does, not when to choose it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.