Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

people_article

Fetch structured article content from a canonical people.com URL, including title, authors, images, timestamps, paywall status, and body paragraphs.

Instructions

Get PEOPLE article content. Returns a PEOPLE article by canonical people.com url, such as https://people.com/example-headline-12345678. The response has title, description, section, authors, lead image, publication and update times, a paywalled flag and body paragraphs. authors is empty for pieces with no byline.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical PEOPLE article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and does meaningful work: it enumerates the returned fields and surfaces the non-obvious `paywalled` flag and the empty-`authors` edge case. It omits anything about caching, rate limits, or failure modes, but for a read-only 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.

Conciseness5/5

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

Three tight sentences, front-loaded with the purpose and then the input contract and response shape. Every sentence adds information; there is no filler.

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?

For a single-param read tool with no annotations and no output schema, the description covers purpose, input format, and the key return fields including the paywall flag. Auth/prerequisites and error behavior are unaddressed, but nothing critical to invoking it correctly is missing.

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; the description adds value by giving a concrete canonical URL example ('https://people.com/example-headline-12345678'), which helps the agent construct or validate the required input beyond the schema's terse 'Canonical PEOPLE article URL'.

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 PEOPLE article content') and names the exact input type (canonical people.com URL). It implicitly separates itself from list-oriented siblings like people_headlines or people_news, but never explicitly differentiates from them, keeping it short of a 5.

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 only implied: the mention of a canonical article URL signals 'fetch one specific article.' There is no explicit when-to-use, when-not-to-use, or named alternative (e.g., people_headlines for browsing, people_author for bylines), so the agent must infer routing.

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