Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reuters_author

Retrieve a Reuters author profile by canonical URL to get name, company, email, social accounts, image, article count, and recent article details.

Instructions

Get a Reuters author profile. Returns a Reuters author's profile by canonical url (https://www.reuters.com/authors/<slug>/): name, company, editorial email, social accounts, profile image, total_articles and the first 20 recent articles, each with title, URL, summary, publication time and an image when the story card has one. Accounts the page does not list are absent.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Reuters 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?

With no annotations, the description carries the full burden and does well: it discloses the returned fields, the 20-article cap ('first 20 recent articles'), and an important data-completeness caveat ('Accounts the page does not list are absent'). It omits auth/rate-limit details, but these are low-stakes for a public profile read.

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-loads the core action in the first sentence, then spends the remainder on return content and caveats. Dense but every clause (field list, 20-item cap, absence note) earns its place; only the exhaustive field enumeration risks bloat.

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, the description appropriately compensates by specifying the return contents and cardinality. Nothing critical is missing for a single-parameter read tool, though a note on how to obtain the canonical URL would close the last gap.

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 baseline is 3, but the description goes beyond the schema's terse 'Canonical Reuters author URL' by giving the concrete URL template 'https://www.reuters.com/authors/<slug>/', which clarifies the expected input format.

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 ('Get') and resource ('Reuters author profile') up front, and the body enumerates exactly what constitutes the profile. It is readily distinguishable from siblings like reuters_article and reuters_news, which return stories rather than an author entity.

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 requirement of a 'canonical url' implies the agent must already hold an author URL, but there is no explicit when-to-use statement and no sibling routing (e.g. no 'to find an author, use ...' vs reuters_articles/reuters_news). Usage is only inferred from the URL shape.

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