Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

guardian_author

Retrieves a Guardian contributor's public profile using a slug or URL, returning their name, bio, Twitter handle, byline image, and recent article list.

Instructions

Get Guardian contributor profile. Returns one Guardian contributor's public profile: name, bio, Twitter handle, byline image, and one page of their recent articles. Provide either the contributor's profile slug or the full profile page URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoCanonical https://www.theguardian.com/profile/<slug> page URL, as an alternative to slug
pageNo1-based article-history page, 1 to 100, defaults to 1
slugNoGuardian contributor profile slug, e.g. hannah-devlin

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 exist, so the description carries full behavioral burden. It does disclose return content and the one-page limitation, but does not cover error behavior, rate limits, or how slug and URL interact when both are provided. No contradiction with annotations.

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 sentences with no filler. The verb and resource are front-loaded, and each sentence contributes either return-field detail or input guidance. Slightly longer than strictly necessary but every sentence earns its place.

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?

No output schema exists, yet the description lists the main return fields and the page default is available in the input schema. For a straightforward profile lookup, it is largely complete; only edge-case behavior (e.g., invalid slug, no results) 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?

Schema description coverage is 100%, so a baseline of 3 applies. The description adds value beyond the schema by clarifying the either/or relationship between slug and URL, which is not stated in the schema properties. It also grounds the page parameter by mentioning 'one page' of recent articles.

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 clear verb ('Get') and resource ('Guardian contributor profile'), and enumerates the specific return fields (name, bio, Twitter handle, byline image, recent articles), making it unambiguous among the many sibling author tools. Does not explicitly contrast with guardian_article or other siblings, so not a 5.

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: when you want a Guardian contributor's profile plus one page of recent articles. The description gives input alternatives (slug or full URL) but does not state when not to use this tool or mention alternatives such as guardian_article, leaving exclusion guidance absent.

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