Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thisismoney_author

Fetch a This Is Money author profile by canonical URL to retrieve name, job title, bio, coverage topics, and recent articles.

Instructions

Get a This Is Money author profile. Returns a This Is Money author's profile by url, a canonical thisismoney.co.uk/profile-<id>/<slug>.html link: name, job title, bio, coverage topic tags such as Money or Bills, and recent articles with title, URL, excerpt and ISO-8601 published_at. job_title and coverage can be empty.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical This Is Money author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the disclosure burden and does well: it lists returned fields, notes that recent articles include title, URL, excerpt and ISO-8601 published_at, and warns that job_title and coverage may be empty. It does not describe pagination, ordering, or invalid-URL behavior, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded, compact, and free of filler. Every sentence adds useful information: purpose, return fields, canonical URL shape, and nullable fields.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with no output schema, the description is complete enough: it explains the expected URL form, enumerates the returned profile fields, describes recent article fields, and discloses which fields may be empty. No structured output schema is present, so the return-value explanation materially supports correct use.

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?

The schema already documents the single url parameter at 100% coverage, so the baseline is 3. The description adds concrete meaning beyond the schema by giving the canonical URL pattern thisismoney.co.uk/profile-<id>/<slug>.html, which helps an agent supply a valid value.

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?

The description states a specific verb and resource: getting a This Is Money author profile, and it enumerates what that profile contains. It clearly distinguishes the tool from generic article/news tools by publisher and by author-profile scope, though it does not explicitly contrast with thisismoney_article.

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 by the required canonical author URL, so an agent knows to call it when it already has an author profile link. However, there is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative for finding articles or sections instead.

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