Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

timesofindia_author

Fetch a Times of India reporter's profile from its canonical author URL, returning name, role, bio, contact details, headshot, and recent articles.

Instructions

Get a Times of India author profile. Returns a Times of India reporter's profile by url, a canonical timesofindia.indiatimes.com/toireporter/author-<name>-<id>.cms link: name, job title, organization, location, email, biography, headshot and recent articles with title and URL. Fields the profile page does not publish may be empty.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Times of India author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/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 disclose the read shape: it lists the profile fields returned (name, job title, organization, location, email, biography, headshot, recent articles) and notes that unpublished fields may be empty. It stops short of error/rate-limit behavior, but for a read-only fetch this is solid disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two sentences, front-loaded with the purpose and followed by the return shape. No filler; every clause adds information.

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 one-parameter read tool with no output schema, the description covers purpose, input format, and return fields, which is enough for correct invocation. Minor gaps remain around how 'recent articles' is bounded or paginated, but nothing blocks a correct call.

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 single `url` param is already documented, but the description adds real value by specifying the canonical URL pattern (timesofindia.indiatimes.com/toireporter/author-<name>-<id>.cms), which tells the agent what a valid input looks like beyond the schema's terse 'Canonical Times of India author URL'.

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 ('Times of India author profile'), and the description makes clear this is the author-profile sibling rather than an article/news/headlines tool. An agent can distinguish it from the many other domain author tools without opening the 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?

Usage is only implied: the tool takes a canonical author URL, so it is usable when such a URL is on hand. No when-not conditions or alternatives (e.g. article or news tools) are named, leaving 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