Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sun_author

Retrieve a The Sun contributor profile from a canonical URL, returning name, job title, bio, and recent articles with titles, excerpts, categories, and links.

Instructions

Get a Sun author profile. Returns a Sun author's profile by url, a canonical thesun.co.uk/author/<slug>/ link: name, job title, bio and recent articles with title, URL, excerpt, category and category URL. job_title is often empty because most Sun bylines carry only a name and bio.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical The Sun 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 returned fields and a data-quality caveat about job_title being often empty, but does not mention auth, rate limits, pagination, or error behavior.

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 return fields and a caveat. Slight redundancy between 'Get a Sun author profile' and 'Returns a Sun author's profile', but overall efficient.

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, so the description must explain returns; it lists key profile fields and recent-article fields and notes a data quirk. It omits limits on 'recent articles' and failure modes, but is reasonably complete for a simple profile getter.

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 already documents the url parameter. The description adds the canonical URL pattern (thesun.co.uk/author/<slug>/), which gives format meaning beyond the schema.

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 'Get' and resource 'Sun author profile', and identifies the canonical URL format. It does not explicitly name sibling tools like sun_article, but the resource and scope are unambiguous.

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?

Provides an implied usage condition—requires a canonical thesun.co.uk author URL—but gives no explicit when-to-use guidance or alternatives to sibling tools such as sun_article or sun_headlines.

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