Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

polygon_author

Fetch a Polygon author profile from its canonical URL to get the author's name, title, bio, image, social links, and latest articles.

Instructions

Get a Polygon author profile. Returns a Polygon author profile by canonical url (https://www.polygon.com/author/<slug>/): name, title, image_url, biography, social links and the articles in the profile's Latest module. Title, image and biography appear only as the profile shows them. social_links holds the author's own accounts, not Polygon's internal follow link.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Polygon author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/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. It discloses that title, image and biography appear only as the profile shows them, and clarifies that social_links refers to the author's own accounts rather than Polygon's internal follow link. It does not cover error handling or authentication, but for a simple read-style profile fetch these omissions are minor.

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?

The description is front-loaded with the core action and return summary, followed by two targeted caveats. Four sentences are used efficiently, though the opening two sentences slightly restate the same author-profile idea.

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?

The tool has one parameter and no output schema, so the description must explain return values. It lists the profile fields (name, title, image_url, biography, social links, latest articles) and adds caveats about how some fields are presented, making it complete enough for an agent to call correctly.

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 description coverage is 100% and the single parameter is already documented as 'Canonical Polygon author URL.' The description adds value by giving the concrete URL template (https://www.polygon.com/author/<slug>/), which removes ambiguity about the expected format.

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?

The description states a specific verb and resource: 'Get a Polygon author profile.' It also names the canonical URL format, and the sibling list contains other author tools for different sites (e.g., kotaku_author, nyt_author), so this is clearly differentiated as the Polygon-specific version.

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?

The usage is implied by 'Get a Polygon author profile' and the required canonical URL, but the description does not explicitly say when to use this tool versus polygon_article or other siblings, nor does it state any exclusions or 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