Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mirror_article

Fetch public Mirror article content by canonical URL, returning title, authors, lead image, dates, paywall status, and body paragraphs. Subscriber-only or blocked articles return an error.

Instructions

Get Mirror article content. Returns a Mirror article by its canonical url: title, description, section, authors, lead image, publication and update times, a paywalled flag and the body paragraphs. Only public content is returned; subscriber-only or blocked articles return an upstream error.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Mirror 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, the description carries the full burden and does well: it enumerates the returned fields (title, description, section, authors, lead image, times, paywalled flag, paragraphs) and discloses an important failure mode — subscriber-only or blocked articles produce an upstream error. It stops short of noting rate limits, auth requirements, or whether the paragraphs are plain text vs HTML.

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?

Two dense sentences with the purpose front-loaded and the field list following. The field enumeration is somewhat long but each item is informative rather than filler, so it earns its space.

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?

No output schema or annotations exist, so the description must cover return shape and failure behavior — and it does both. The remaining gap is minor: it doesn't mention authentication, rate limits, or the format of the paragraph body.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Single parameter with 100% schema description coverage, so the schema already defines `url` as the canonical Mirror article URL. The description echoes 'canonical' but adds no format examples or detail beyond the schema — baseline 3 fits.

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?

Specific verb+resource ('Get Mirror article content') with scope stated as a single-article fetch by canonical URL. Sibling tools are mirror_headlines/mirror_news/mirror_sections/mirror_author, and the 'article by its canonical url' framing clearly separates it from those list-level tools.

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 'by its canonical `url`' phrasing and the return of full body content, which signals a detail-retrieval tool rather than a listing tool. It does not explicitly state when to prefer this over siblings like mirror_headlines or mirror_sections, nor any preconditions.

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