Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

news18_author

Retrieve a News18 author profile from a canonical byline URL, returning name, biography, image, social links, and recent articles with UTC publish dates.

Instructions

Get a News18 author profile. Returns a News18 author profile from a required url in the form https://www.news18.com/byline/<slug>.html. The response has name, biography, image_url, social_links (whichever of website, X/Twitter, Facebook, Instagram, YouTube and LinkedIn are set) and recent articles with published_at in RFC3339 UTC. Wire and staff bylines often have no bio or links.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical News18 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 details the return shape (name, biography, image_url, social_links, recent articles) and proactively warns that 'wire and staff bylines often have no bio or links.' It omits auth needs, rate limits, and error behavior, so it stops short of a 5.

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?

Four sentences, front-loaded with the verb+resource, then input format, then return shape, then an edge-case caveat. Efficient overall, though 'Get a News18 author profile' and 'Returns a News18 author profile' are mildly redundant.

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 and no annotations, the description handles the load by enumerating return fields and flagging the empty-bio case. It leaves the count/pagination of 'recent articles' and error handling unspecified, so it is strong but not fully 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 the baseline is 3, but the description adds a concrete URL pattern ('/byline/<slug>.html') that goes beyond the schema's vague 'Canonical News18 author URL.' This syntactic detail is genuinely useful for constructing a valid request.

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 and resource ('Get a News18 author profile') and is trivially distinguishable from siblings like news18_article, news18_news, and news18_sections. The scope is exact — a single author profile keyed by URL.

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 via the required URL form ('https://www.news18.com/byline/<slug>.html'), which tells the agent what input is expected, but it never states when to prefer this over siblings or what condition selects an author lookup. No exclusions or alternatives are given.

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