Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

businessstandard_author

Fetch a Business Standard author profile and recent stories from a canonical author URL, returning bio, social links, and premium flags.

Instructions

Get a Business Standard author profile. Returns a Business Standard author's profile from url, a canonical https://www.business-standard.com/author/<slug> address: name, designation, biography, image, and Twitter, Facebook, LinkedIn and YouTube links where listed, plus about 20 recent stories. Stories carry a title, URL and optionally summary, date and a premium flag for subscriber-only text. An unknown author returns 404.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Business Standard author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations, so the description must carry the behavioral burden, and it does well: it enumerates returned profile fields, ~20 recent stories, per-story fields (title, URL, optional summary, date, premium flag) and the 404 on unknown authors. It omits auth/rate-limit context, keeping it just 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.

Conciseness5/5

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

Three tightly written sentences, front-loaded with the core action, then return shape, then the edge case. No filler.

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?

With no output schema and no annotations, the description fully covers what an agent needs: purpose, input URL format, returned fields, and 404 handling. Nothing essential is missing for a read-only profile fetch.

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 value by explaining the URL is a canonical `https://www.business-standard.com/author/<slug>` address, clarifying the expected format beyond the schema's short 'Canonical Business Standard 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 ('a Business Standard author profile') and clarifies the input is a canonical author URL. An agent can distinguish it from businessstandard_article/news/headlines siblings at a glance.

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 required canonical URL rather than stated; there is no explicit when-to-use, when-not, or named alternative. For a single author-profile endpoint this is acceptable but not instructive.

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