Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vox_author

Fetch a Vox author profile from a canonical URL to retrieve name, job title, bio, and recent articles with metadata.

Instructions

Get a Vox author profile. Returns a Vox author profile from their canonical url (www.vox.com/authors/<slug>, required). The response has the name, job_title from the masthead (such as Senior Politics Correspondent), bio and recent articles, each with title, URL, excerpt, category and an ISO-8601 published_at.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Vox author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses the full response shape (name, job_title, bio, recent articles with fields), which is genuinely useful, but it does not state permissions, rate limits, or that the operation is read-only beyond the implicit "Get".

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

Conciseness4/5

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

Front-loaded with purpose, then input format, then return fields. Two efficient sentences, though the trailing enumeration of article fields is slightly over-detailed for a tool with no output schema.

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 single-parameter read tool with no annotations and no output schema, the description covers purpose, input format, and response contents adequately. Only explicit when-to-use routing guidance 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?

With 100% schema coverage the baseline is 3, and the description goes beyond the schema by giving the concrete URL pattern `www.vox.com/authors/<slug>` rather than just "Canonical Vox author URL", which helps the agent construct a valid 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 a Vox author profile") and clarifies it fetches by canonical url. It's clearly distinguishable from vox_article/vox_headlines/vox_sections by resource, though it never names a sibling explicitly.

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 by the required canonical author URL, but there is no explicit when-to-use guidance or comparison to the close siblings (vox_article, vox_news). An agent can infer the purpose but gets no routing help.

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