Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

theverge_author

Fetch a The Verge author profile by canonical URL to get name, job title, bio, and recent articles with titles, links, dates, and categories.

Instructions

Get a The Verge author profile. Returns a The Verge author's profile by url, a canonical theverge.com/authors/<slug> link: name, job title such as Senior Reporter, bio and recent articles. Each article has a title, URL, excerpt, ISO-8601 published_at and category, the post's primary Verge vertical such as Tech.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical The Verge author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the return shape in useful detail, but omits operational behavior such as how many recent articles are returned, pagination, error handling for invalid URLs, and any auth or rate-limit constraints. Read-only behavior is only implied by '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 and compact, with the purpose stated first and return details following. The first sentence is slightly redundant with the start of the second, but overall the description is efficient and every clause adds useful information, especially since there is 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 simple one-parameter read tool with full schema coverage and no output schema, the description gives enough return detail for correct invocation. It would be stronger with article-count/pagination or error behavior, but the missing pieces are minor for this tool's complexity.

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 format guidance: the URL is a canonical 'theverge.com/authors/<slug>' link. That helps an agent validate or construct the required parameter beyond the schema's brief 'Canonical The Verge author URL' text.

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 The Verge author profile') and clearly distinguishes the tool's output from article- or news-focused siblings by describing a profile with bio and recent articles. The return fields are concrete enough that an agent can identify it as the author-profile tool 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 Guidelines2/5

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

The description explains what is returned but gives no explicit when-to-use guidance, no alternatives (e.g., theverge_article, theverge_news), and no prerequisites beyond the canonical URL format. Usage is only weakly implied by the purpose and parameter.

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