Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cbsnews_article

Fetch a CBS News article by its canonical URL and return structured JSON, including title, description, publication times, authors, section, lead image, and body paragraphs.

Instructions

Get CBS News article content. Returns a CBS News article by url, a canonical HTTPS cbsnews.com/news/<slug> address. The response has the title, description, publication and update times, authors, section, lead image and the body paragraphs.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical CBS News article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations and no output schema, the description carries the full burden and does real work by enumerating the returned payload (title, description, publication/update times, authors, section, lead image, body paragraphs). It does not cover auth, rate limits, or error behavior, but for a read-only content getter the return-shape disclosure is the important missing context and it is provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and resource, then the required input form and return shape. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no output schema, the description supplies everything needed: what it fetches, the exact URL contract, and the response fields. Nothing material to calling it correctly is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already labels the url as a 'Canonical CBS News article URL', so baseline is 3. The description goes slightly beyond by spelling out the accepted form (HTTPS cbsnews.com/news/<slug>), which helps an agent validate or construct the input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get CBS News article content... Returns a CBS News article by url') and the URL form, which distinguishes it from the cbsnews_headlines/news/sections siblings by being the single-article detail endpoint. It does not explicitly name a sibling to differentiate against, so it stops short of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by specifying the required input must be a canonical HTTPS cbsnews.com/news/<slug> address, which tells the agent what it must supply. However, it never states when to choose this over cbsnews_headlines or cbsnews_news, so usage is only implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools