Crawlora MCP

cbc_author

Read-only

One CBC journalist's public profile: name, job title, biography, photo, profile links, and their most recent articles, from an author slug or canonical cbc.ca/author/ URL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cbc_author"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No	Canonical https://www.cbc.ca/author/<slug> URL; alternative to slug
`slug`	No	Author slug, e.g. darren-major-1.4462710

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 7, 2026

addedInput schema / properties / slug / description

Added value: +"Author slug, e.g. darren-major-1.4462710"

addedInput schema / properties / url / description

Added value: +"Canonical https://www.cbc.ca/author/<slug> URL; alternative to slug"

First observedOct 5, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds one useful behavioral detail, that the response bundles the author's most recent articles alongside the profile, but says nothing about permissions, rate limits, or how many articles are returned.

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?

A single well-formed sentence with the resource front-loaded and the accepted input forms trailing; no redundant or filler language.

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

Completeness4/5

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

For a read-only lookup with an output schema, the description covers the resource, the payload contents, and both accepted input forms. The only minor gap is not stating that at least one of the two optional parameters must be supplied.

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

Parameters3/5

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

Schema description coverage is 100% and both parameters are already documented with examples (darren-major-1.4462710). The description restates that either a slug or a canonical URL works but adds no syntax or format detail beyond the schema.

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?

The description names a specific verb (retrieves) and resource (one CBC journalist's public profile) and enumerates what the profile contains, including recent articles. An agent can immediately distinguish it from cbc_article, cbc_headlines, cbc_news and cbc_sections.

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?

Usage is implied: use it when you need a CBC author's profile or their recent output, and the inputs must be an author slug or a canonical cbc.ca/author/<slug> URL. There is no explicit when-not guidance or comparison to sibling tools, but the use case is unambiguous.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?