Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cbc_author

Get a CBC journalist profile by slug or URL. Returns name, title, biography, photo, profile links, and latest articles.

Instructions

Get a CBC journalist profile. Returns a CBC journalist's profile, identified by slug (ending in CBC's author id, such as darren-major-1.4462710) or a https://www.cbc.ca/author/<slug> url; exactly one is required and an unknown author returns 404. The response has name, title, biography, photo, profile links and usually 10 latest articles, with has_more_articles showing whether older ones exist.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical https://www.cbc.ca/author/<slug> URL; alternative to slug
slugNoAuthor slug, e.g. darren-major-1.4462710

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it discloses the 404 behavior for unknown authors, the exact-one-of input constraint, and the shape of the payload including the 10-article cap and the has_more_articles pagination signal. It omits any rate-limit or auth context, which keeps it short of a 5.

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?

Three sentences, front-loaded with the purpose and then layering the identifiers, failure mode, and return shape. Every clause carries information an agent needs; nothing is redundant with the schema.

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 two-parameter lookup with no output schema and no annotations, the description covers retrieval semantics, input constraint, error behavior, and response contents including pagination. There is no material gap an agent would need to guess at.

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%, so the baseline is 3, but the description adds meaningful semantics the schema cannot express: the 'exactly one is required' XOR constraint between url and slug, neither of which is marked required. It also clarifies the slug format (site-qualified, ending in a CBC numeric id) beyond the schema's bare example.

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+resource ('Get a CBC journalist profile') and immediately scopes it as returning a journalist's profile identified by slug or URL. An agent can distinguish it from cbc_article, cbc_headlines, and cbc_news without opening the schema.

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

Usage Guidelines4/5

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

Explicitly states that exactly one of slug or url is required and that an unknown author returns 404, which tells the agent how to invoke and what failure looks like. It does not name sibling alternatives (e.g., when to prefer this over cbsnews_author), but within the CBC namespace the selection is unambiguous.

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