Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

collider_article

Fetch a single Collider article's content by its canonical URL, returning title, metadata, authors, lead image, and body paragraphs; reject section, video, or author pages.

Instructions

Get Collider article content. Returns one Collider article by its url, which must be a single-segment https://collider.com/<slug>/ address. The response has the title, description, publish and update times, section, authors, lead image and body paragraphs. Section hubs and video or author pages are rejected as invalid parameters.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Collider article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/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, and it does disclose the return shape (title, description, publish/update times, section, authors, lead image, body paragraphs) plus validation behavior (single-segment URL required). It omits operational details like auth needs or rate limits, but for a read-only fetcher with no output schema the disclosure is strong.

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 sentences, front-loaded with the core action, then the identifier format, then the return contents. No wasted words; each sentence carries distinct information.

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-required-param read tool with no output schema and no annotations, the description covers purpose, valid input format, rejection cases and return fields. Nothing an agent needs to invoke 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, but the description adds real meaning the schema lacks: the URL must be a 'single-segment https://collider.com/<slug>/' address and hub/video/author URLs are rejected. This format constraint goes beyond the schema's generic 'Canonical Collider 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 Collider article content', 'Returns one Collider article by its url') and pins the exact scope: a single article identified by its slug URL. This cleanly distinguishes it from siblings like collider_author, collider_news and collider_sections, which the description implies are not what this tool returns.

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 clear when-not guidance by stating that 'Section hubs and video or author pages are rejected as invalid parameters', which steers the agent away from misusing section/author URLs. It does not explicitly name the sibling tools to use instead (e.g., collider_author, collider_sections), so it stops short of full alternative 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