Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

indiatoday_author

Fetch an India Today author profile by URL to get name, title, headshot, bio, and recent stories with titles, sections, summaries, and images.

Instructions

Get an India Today author profile. Returns an India Today author profile by url, a canonical https://www.indiatoday.in/author/<slug> link; desk bylines such as india-today-business-desk work too. The response has the name, job title, headshot, biography and the first page of recent text stories (typically 20), each with title, URL, section, summary and image. Stories carry no dates.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical India Today 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 it well: it discloses the response contents (name, job title, headshot, biography, recent stories), the page size (typically 20), the per-story fields, and the important caveat that stories carry no dates. It omits whether/how additional pages can be fetched, which is the main remaining behavioral gap.

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 tight sentences, front-loaded with purpose then input format then response shape. Slight redundancy between 'Get an India Today author profile' and 'Returns an India Today author profile by url', but nothing is wasted and the 'stories carry no dates' caveat earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description must describe both behavior and return payload; it does both in detail, including the first-page/typical-20 limit and the fields per story. For a single-parameter read tool this is complete enough to call correctly without further inference.

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% for the single required 'url' parameter, so the baseline is 3. The description adds genuine meaning beyond the schema's terse 'Canonical India Today author URL' by giving the concrete URL shape (https://www.indiatoday.in/author/<slug>) and confirming desk bylines are valid inputs.

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?

The opening sentence states a specific verb and resource ('Get an India Today author profile'), and the tool name plus description make the scope unambiguous among the indiatoday_* family (article/headlines/news/sections). An agent can tell this fetches a byline profile rather than content listings.

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 resource type, and the note that desk bylines such as 'india-today-business-desk' are accepted is a useful input hint. However, there is no explicit when-to-use guidance and no routing to alternatives (e.g., use indiatoday_article for a single story), which matters given the many sibling tools.

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