Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

japantimes_author

Fetch The Japan Times author profile and linked article cards from a canonical /author/// URL, returning name, titles, summaries, images, and publication times.

Instructions

Get a The Japan Times author profile. Returns a The Japan Times author's name and the article cards linked from their profile page. url is required and must be a canonical HTTPS profile link in the form /author/<numeric-id>/<slug>/. Each article has a title, URL, summary, author, image, type and publication time. Paginated /page/<n>/ URLs are not followed.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical HTTPS /author/<numeric-id>/<slug>/ profile URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does so reasonably: it discloses the return contents (author name plus article cards), the exact URL shape required, and a real behavioral constraint (paginated URLs are not followed). It omits auth/rate-limit details, but for a read-only profile fetch this is solid disclosure.

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, followed by return contents and then the input constraint. Three sentences, all earning their place, with only minor repetition of 'The Japan Times author'.

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, and the description compensates by enumerating the fields each article card carries (title, URL, summary, author, image, type, publication time). Combined with the URL-format and pagination notes, an agent has enough to call this correctly; only auth/error behavior is unaddressed.

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% and there is a single parameter, so the schema already documents `url`. The description still adds value beyond the schema by specifying the canonical /author/<numeric-id>/<slug>/ form and the important exclusion of paginated URLs. That extra semantic guidance lifts it above the baseline 3.

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 ('Get') and resource ('The Japan Times author profile') and distinguishes itself from sibling tools like japantimes_article, japantimes_news, and japantimes_sections. An agent can immediately tell this returns an author's profile and their article cards.

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 description constrains the input ('url is required and must be a canonical HTTPS profile link') and notes that paginated /page/<n>/ URLs are not followed, which is useful context. However, it never explicitly states when to use this tool versus alternatives such as japantimes_article, so usage is only implied.

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