Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cbssports_author

Fetch a CBS Sports writer profile using a slug or URL, returning name, title, bio, social link, and recent article titles, URLs, and summaries.

Instructions

Get a CBS Sports writer profile. Returns a CBS Sports writer's profile, identified by slug (such as david-cobb) or a cbssports.com/writers/<slug>/ url; exactly one is required and an unknown slug returns not-found. The response has name, title, headshot, bio, X/Twitter link and about 15 recent articles with title, URL and summary. Profile fields the page lacks are omitted.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical cbssports.com/writers/<slug>/ URL; alternative to slug
slugNoWriter slug, e.g. david-cobb

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that an unknown slug produces a not-found result and that profile fields absent from the page are omitted. It doesn't mention auth or rate limits, but the error and omission behaviors are the key traits an agent needs.

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?

Front-loaded with the purpose, then inputs, then response shape in three tight sentences with no filler. Every clause earns its place.

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?

There is no output schema, so the description correctly summarizes the return payload (name, title, headshot, bio, X/Twitter link, ~15 recent articles) and the omission behavior. Nothing an agent needs to call it correctly is missing.

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% (baseline 3), and the description adds real value beyond the schema: the mutual-exclusivity constraint 'exactly one is required' and a concrete slug example ('david-cobb'), plus the url format.

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

Purpose5/5

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

States a specific verb and resource ('Get a CBS Sports writer profile') and clearly distinguishes itself from the sibling article/headlines/news/sections tools. An agent can immediately tell this is the writer-profile lookup.

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 tells you how to identify the writer (slug or url, exactly one) but gives no explicit when-to-use versus alternatives or any prerequisites. Usage is only implied by the tool's narrow scope.

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