Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

economictimes_author

Fetch an Economic Times author profile from a canonical reporter URL, returning name, role, biography, headshot, and recent articles with links.

Instructions

Get an Economic Times author profile. Returns an Economic Times reporter profile for a url like https://economictimes.indiatimes.com/etreporter/author-<name>-<id>.cms. The response has the name, job title (role and desk in one string), biography, headshot and recent articles with title and URL. Job title, biography and image may be empty; no email field exists.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Economic Times 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. It transparently lists what the response contains (name, job title, biography, headshot, recent articles) and notes that some fields may be empty and no email exists. This is useful behavioral context, though it omits rate limits or auth requirements.

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?

The description is four sentences, front-loaded with the core action, then the URL format, then response details and caveats. Every sentence adds useful information without redundancy.

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 adequately explains the return values and their limitations. It could mention pagination or the number of recent articles, but for a simple profile-fetch tool it is nearly complete.

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. The description adds value by showing an example URL pattern (`https://economictimes.indiatimes.com/etreporter/author-<name>-<id>.cms`), which clarifies the expected format beyond the schema's generic 'Canonical Economic Times 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 ('Economic Times author profile'), and clarifies it returns a reporter profile. The URL pattern further distinguishes it from sibling tools like economictimes_article or economictimes_headlines.

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 description implies usage by specifying the required URL format, but it does not explicitly say when to use this tool versus alternatives (e.g., other ET tools or other author-profile tools). No exclusions or comparison to siblings are provided.

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