Crawlora MCP

cnbc_author

Read-only

Fetch one CNBC author's public bio page: name, job title, biography, social links, and their most recent articles. Use cnbc_article for one story's content. Use cnbc_headlines for current outlet feeds.

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": "cnbc_author"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No	Canonical https://www.cnbc.com/<slug>/ author page URL, as an alternative to slug
`slug`	No	CNBC author slug, e.g. jeff-cox

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: +"CNBC author slug, e.g. jeff-cox"
```

addedInput schema / properties / url / description

Added value: +"Canonical https://www.cnbc.com/<slug>/ author page URL, as an alternative to slug"

First observedOct 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful scope context by specifying exactly what the bio page exposes (bio fields plus most recent articles), though it says nothing about pagination limits on 'most recent articles'. A solid addition over the annotation baseline.

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 tight sentences: purpose first, then two routing sentences. Every clause earns its place with no filler, and the most important information is front-loaded.

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?

With an output schema present, return values need no explanation, and annotations carry the safety profile. The description covers purpose and routing fully; the only minor gap is not hinting at how to obtain a slug/URL or how many 'most recent articles' are returned.

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%, with both 'url' and 'slug' fully documented in the schema, including that url is an alternative to slug. The description doesn't mention either parameter, so it adds no meaning beyond the schema; baseline 3 is appropriate.

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 ('Fetch') and precise resource ('one CNBC author's public bio page') and enumerates the returned contents (name, job title, biography, social links, recent articles). It explicitly distinguishes itself from cnbc_article and cnbc_headlines, so the agent can route without opening schemas.

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

Usage Guidelines5/5

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

Names both alternatives explicitly and gives the condition that selects each: cnbc_article for a single story's content, cnbc_headlines for current outlet feeds. The when-to-use-vs-alternatives guidance is unambiguous and leaves nothing to inference.

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?