Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kotaku_author

Fetch a Kotaku author profile from a canonical URL, returning name, biography, image, social links, and recent articles.

Instructions

Get a Kotaku author profile. Returns a Kotaku author profile by url, a canonical https://kotaku.com/author/<slug> link. The response has the name, biography, image_url, social_links (a type label and URL) and recent articles. The article published_at is the page's own date text, such as Published September 23, 2026 at 11:20 am, not a timestamp.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Kotaku 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 carries the full burden and does disclose the response shape (name, biography, image_url, social_links, recent articles) plus a subtle behavioral quirk: published_at is raw page date text, not a timestamp. It omits permission/auth/rate-limit context, but for a public read endpoint it adds meaningful value beyond structured fields.

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?

Front-loaded with the core purpose in one clause, then return-field detail. Mostly efficient; the published_at example is slightly long but earns its place by preventing a format misread.

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?

For a single-parameter read tool with no output schema and no annotations, the description covers the purpose, input format, and returned fields adequately. The main missing piece is guidance on how to obtain a valid author URL.

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 by specifying the canonical form `https://kotaku.com/author/<slug>`, which tells the agent the expected URL pattern rather than just 'canonical author URL'.

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 Kotaku author profile') and names the exact input shape. It is clearly distinguishable from Kotaku siblings like kotaku_article, kotaku_news, and kotaku_headlines by being author-profile-oriented, though it never explicitly contrasts them.

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 only implied: you supply a canonical author URL and get that author's profile. There is no explicit when-to-use statement, no prerequisites, and no routing to alternatives such as kotaku_article for a specific piece.

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