Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

indianexpress_author

Fetch a The Indian Express author profile by canonical URL, returning name, image, biography, and recent articles with titles, links, summaries, and images.

Instructions

Get a The Indian Express author profile. Returns a The Indian Express author's profile by url, a canonical indianexpress.com/profile/author/<slug>/ link: name, image URL, biography and recent articles with title, URL, summary and image. image_url and biography may be missing, and published_at is the page's date text such as Sep 24, 2026 16:36 IST, not a timestamp.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical The Indian Express author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/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 add real behavioral context: it discloses that image_url and biography may be missing and that published_at is page date text ('Sep 24, 2026 16:36 IST'), not a timestamp. It omits error/invalid-URL behavior and pagination of recent articles, keeping it below the top band.

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 the purpose, then supporting detail. Every clause earns its place given there is no output schema. The enumeration of return fields and caveats is dense but not padded.

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 annotations and no output schema, the description compensates well by describing the profile's returned fields, the nested recent-article fields, nullability of image_url/biography, and the date-text format. Only pagination/error behavior is unaddressed, which is minor for a single-URL read.

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% (baseline 3), and the description adds format meaning beyond the schema's 'Canonical ... author URL' by giving the concrete indianexpress.com/profile/author/<slug>/ pattern. This is a genuine value-add over the structured field.

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+resource ('Get a ... author profile') and the site, so it is clearly distinguishable from indianexpress_article/news/sections siblings. It does not explicitly name an alternative sibling, but the resource type makes the purpose 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?

No explicit when-to-use or when-not guidance relative to alternatives. It does supply a precondition for the input ('a canonical indianexpress.com/profile/author/<slug>/ link'), which gives partial usage context, but selection guidance is left 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