Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

mediaite_author

Retrieve a Mediaite author profile by slug or URL to get bio, contact details, and recent articles.

Instructions

Get a Mediaite author profile. Returns a Mediaite author profile by slug (for example michael-luciano) or by a mediaite.com author url; supply exactly one. The response has name, bio, avatar_url, email, twitter and about 10 recent articles, each with title, url and a short date label such as Sep 24th (no year or time). Contact fields are omitted when the page shows none.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical mediaite.com/author/<slug>/ URL; alternative to slug
slugNoAuthor slug, e.g. michael-luciano

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it enumerates the returned fields (name, bio, avatar_url, email, twitter, ~10 recent articles) and flags two behavioral quirks — the date label has no year/time, and contact fields are omitted when the page shows none. It does not cover auth, rate limits, or failure modes, 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.

Conciseness4/5

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

Front-loaded with the action, then input rules, then response shape. Dense but waste-free; only the 'for example michael-luciano' clause slightly duplicates the slug schema description.

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 two-parameter lookup with no annotations and no output schema, the description covers inputs, exclusivity rule, and the full response shape including caveats. Only absence of any error/empty-result behavior keeps it from full completeness.

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. The description still adds value beyond the schema by stating that the two parameters are mutually exclusive and that exactly one must be supplied, plus a concrete slug example — information the schema does not express.

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?

Names a specific verb and resource ('Get a Mediaite author profile') and immediately scopes it to lookup by slug or canonical URL. An agent can distinguish it from mediaite_headlines, mediaite_news, mediaite_sections and mediaite_article without opening another schema.

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?

The description does state the mutually-exclusive input rule ('supply exactly one'), which is real usage guidance. However, it never says when this tool is preferred over sibling endpoints (e.g. versus mediaite_article for a specific story), so routing guidance is only implied.

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