Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

punch_article

Retrieve structured Punch article content by canonical URL, including title, metadata, authors, image, and body paragraphs for reading or analysis.

Instructions

Get Punch article content. Returns a Punch article by canonical url (https://punchng.com/<slug>/): title, description, publication and update times, section, authors, image and the body paragraphs. Punch articles are free to read, so paywalled is never set. Video-led stories may have only a short text summary.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Punch article 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?

With no annotations, the description carries the full burden and delivers real behavioral context: it lists the returned fields, states that 'paywalled' is never set (free access), and warns that video-led stories may return only a short text summary. It omits error behavior for malformed URLs and any rate/access constraints, keeping it 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?

Front-loads the purpose in the first clause, then layers return fields, access status, and the video-story caveat. Three sentences, every one carrying distinct information, no padding.

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 one-parameter read tool with no output schema, the description compensates well: it enumerates the return payload (title, description, times, section, authors, image, paragraphs) and flags the content-completeness pitfall for video-led pieces. Nothing essential to calling or interpreting the result 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?

Single required param with 100% schema coverage, so the baseline is 3. The description earns above baseline by giving the concrete URL pattern 'https://punchng.com/<slug>/', which clarifies what 'canonical' means beyond the schema's terse 'Canonical Punch article 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 Punch article content') and names the exact retrieval unit, an article by URL. An agent can immediately separate this from punch_headlines/punch_news/punch_sections, which list rather than fetch a single story.

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?

It implies when to use it by specifying the required canonical URL format ('https://punchng.com/<slug>/'), which tells the agent it needs a known URL rather than a query. However, it never explicitly routes the agent to punch_headlines or punch_sections to discover URLs, and gives no 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