Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

ign_author

Fetch an IGN author profile from a canonical IGN person URL, returning name, job title, bio, location, social links, headshot, and recent articles.

Instructions

Get an IGN author profile. Returns an IGN author profile by url, a canonical https://www.ign.com/person/<username> link. The response has the username, name, job title, location, biography, headshot, social_links (platform and URL) and the author's recent articles.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical www.ign.com/person/<username> URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully enumerates the returned payload (username, name, job title, location, biography, headshot, social_links, recent articles), which is real value beyond the schema. It still omits any behavioral notes such as error behavior for invalid/missing URLs or whether the resource is public.

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 sentences, front-loaded with the purpose, then the input format, then the response shape. It is efficient and each sentence carries distinct information, though the input-format sentence mildly repeats the schema description.

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?

With no output schema, the description must describe return values, and it does so by listing the response fields, which is appropriate for a simple single-parameter read tool. The main gap is the absence of any error or existence caveats, but overall it is complete enough to call correctly.

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?

Schema description coverage is 100% and there is a single parameter, so the schema already documents `url` as a canonical person URL. The description reinforces the same canonical `https://www.ign.com/person/<username>` format but adds no syntax or validation detail beyond the schema, so the baseline of 3 is correct.

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 ('Get') and resource ('IGN author profile'), which is unambiguous and lets an agent identify the tool. However, it does not differentiate from the many sibling `*_author` tools (kotaku_author, nyt_author, etc.) or explain its relationship to ign_article and ign_news, so sibling disambiguation relies on the tool name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the required input shape ('by url') but gives no when-to-use guidance, no when-not-to-use, and does not name any alternative tool. Nothing tells the agent why it would pick this over fetching the author's articles via another IGN endpoint.

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