Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

telegraph_author

Fetch a Telegraph author profile from a canonical URL to get their name, job title, bio, and recent articles with titles, links, excerpts, and publication dates.

Instructions

Get a Telegraph author profile. Returns a Telegraph author's profile by url, a canonical telegraph.co.uk/authors/<letter>/<range>/<name>/ link: name, job title, bio and recent articles with title, URL, excerpt and ISO-8601 published_at. job_title can be empty for contributors without a masthead credit.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Telegraph author URL

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?

No annotations are provided, so the description carries the disclosure burden and does so reasonably: it enumerates exactly what is returned (name, job title, bio, recent articles with excerpt and ISO-8601 published_at) and flags the edge case that `job_title` can be empty. It omits pagination/how many articles and any error behavior for non-author URLs, keeping it from 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?

Three front-loaded sentences with no filler; the core purpose leads. Slightly dense on field enumeration, but that is justified given 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?

With no output schema and no annotations, the description succeeds at conveying the return shape and a field edge case. The only gap is not stating how many 'recent articles' are returned or whether pagination exists.

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% and the schema already labels the single parameter, so baseline would be 3. The description adds real value by spelling out the canonical URL pattern (`telegraph.co.uk/authors/<letter>/<range>/<name>/`), which the schema does not provide, reducing malformed calls.

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 Telegraph author profile') and immediately distinguishes itself from article/headline siblings by scope. An agent can tell this fetches an author entity rather than content.

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-URL constraint, but there is no explicit when-to-use guidance, no statement of alternatives (e.g., telegraph_search or article tools to find an author URL), and no exclusions. Adequate but leaves routing to inference.

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