Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

marketwatch_author

Retrieve a MarketWatch author profile by slug or canonical URL to get the writer's name, title, bio, employer, and a page of recent articles with clean links.

Instructions

Get a MarketWatch author profile. Returns a MarketWatch author profile, identified by slug (such as hannah-pedone) or a canonical marketwatch.com/author/<slug> url; provide exactly one. The response has the name, job title, bio, works_for and one page of recent articles with title and URL. The ?mod= attribution query is removed from article URLs.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical marketwatch.com/author/<slug> URL; alternative to slug
slugNoAuthor slug, e.g. hannah-pedone

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 safety/behavior burden and does well: it discloses the returned fields (name, job title, bio, works_for, one page of recent articles) and a non-obvious normalization behavior ('?mod=' attribution query is removed from article URLs). It does not cover failure modes for an invalid slug/url or pagination limits.

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 tight sentences, front-loaded with purpose, then identity inputs, then return shape. Every sentence adds information; nothing is padded.

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, the description is the sole source for return values and handles it (profile fields plus recent articles with title/URL). Combined with the identity rules, an agent has enough to invoke it correctly.

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 already 100%, so the 3 baseline applies, but the description adds real value: a concrete slug example (`hannah-pedone`), the canonical URL form, and the mutual-exclusivity rule that the schema alone does not enforce.

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 and resource ('Get a MarketWatch author profile') and the input identity mechanism. It is clearly distinct from the adjacent marketwatch_article/headlines/news/sections siblings by resource type, though it never explicitly names or contrasts with them.

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?

Gives an explicit selection rule between the two inputs ('provide exactly one' of `slug` or `url`) with a concrete format for each. It stops short of stating when to prefer this tool over the sibling article/headline tools, so it clears context but not full when-not guidance.

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