Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

livemint_author

Fetch a Mint author profile from a required canonical livemint.com/authors URL, returning name, job title, biography, image, and social links; it excludes articles.

Instructions

Get a Mint author profile. Returns a Mint author profile from a required url in the form https://www.livemint.com/authors/<slug>. The response has name, job_title, biography, image_url and Twitter, Facebook, LinkedIn and Instagram links, each present only when the profile carries it. It does not list the author's articles.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Mint author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden; it does so reasonably by disclosing the exact response fields (name, job_title, biography, image_url, social links) and the conditional presence of those fields. It omits failure modes (e.g., invalid slug) and any auth/rate-limit notes, but for a simple read fetch this is solid disclosure.

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 purpose and only three sentences, all earning their place except a minor redundancy where 'Get a Mint author profile' is restated as 'Returns a Mint author profile'. Efficient overall.

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?

For a single-parameter fetch with no output schema, the description supplies the missing return-value information (enumerated fields and their conditional presence) plus a scope boundary, so nothing an agent needs to invoke it correctly is absent.

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?

With one fully described parameter, the baseline is 3, and the description adds real value by giving the exact URL form 'https://www.livemint.com/authors/<slug>' and marking it required, which goes beyond the schema's terse 'Canonical Mint 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 and resource ('Get a Mint author profile') and immediately scopes it by clarifying it does not list the author's articles, which disambiguates it from livemint_article and other content-list siblings. An agent can tell what it returns without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear usage context (fetch a profile from its canonical URL) and an explicit exclusion ('does not list the author's articles'), which implicitly routes article requests elsewhere. It stops short of naming the alternative tool, so it falls just under a full when/when-not/alternatives treatment.

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