Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

collider_author

Retrieve a Collider author profile from a canonical URL, returning biography, social links, and roughly 20 latest articles.

Instructions

Get a Collider author profile. Returns a Collider author profile for a url of the form https://collider.com/author/<slug>/. The response has the name, title, image, biography, social_links (type and URL) and the roughly 20 latest articles on the profile. Paginated author URLs are rejected, so older articles are not available.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Collider author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description does the heavy lifting well: it enumerates the returned fields (name, title, image, biography, social_links, ~20 latest articles) and discloses a real constraint that paginated author URLs are rejected so older articles are unavailable. Auth requirements aren't mentioned, but this is a strong disclosure for a read tool.

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?

Three compact sentences with the key constraint (pagination rejection) front-loaded alongside the return contents. Slight redundancy between 'Get a Collider author profile' and 'Returns a Collider author profile' costs a point.

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 exists, so the description correctly compensates by listing the response fields and the article-limit behavior. Combined with the URL format and pagination caveat, an agent has enough to call it correctly and interpret results.

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 baseline is 3, but the description adds real meaning beyond the schema's 'Canonical Collider author URL': it gives the exact pattern `https://collider.com/author/<slug>/` and states that paginated forms are rejected. That's useful semantic detail the schema lacks.

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 Collider author profile.' The agent can tell it apart from article/news siblings at a glance. It stops short of explicitly naming a sibling, but the author-profile scope is unambiguous.

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 only – it tells you the URL form to pass but not when to choose this over collider_article or another author tool. No explicit when-to-use or when-not guidance is given.

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