Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bloomberg_author

Fetch a Bloomberg author's profile from a canonical URL. Get name, title, bio, and recent articles with bylines and timestamps.

Instructions

Get a Bloomberg author's profile. Returns a Bloomberg author's profile from url, a canonical https://www.bloomberg.com/authors/<id>/<slug> address, where <id> is an opaque token Bloomberg assigns and cannot be guessed. The response has name, title, bio and recent content with title, URL, type, section, full byline and publication and update times.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Bloomberg 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?

With no annotations, the description carries the full burden, and it does disclose the response contents (name, title, bio, recent content with title/URL/type/section/byline and timestamps). It implies a read-only fetch but says nothing about auth requirements or rate limits, so it stops short of full behavioral coverage.

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 URL contract, then the return shape. Nothing is padded, though the final enumerative sentence is somewhat dense and could be tightened.

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 and no annotations, the description supplies the missing return-shape and parameter-format information an agent needs. It is nearly complete for a single-param profile fetch, with only auth/error behavior left 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 the schema only says 'Canonical Bloomberg author URL', but the description adds real meaning: the exact URL pattern `https://www.bloomberg.com/authors/<id>/<slug>` and the critical fact that the `<id>` is opaque and unguessable. That materially changes how an agent must obtain the value.

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 and resource ('Get a Bloomberg author's profile') and describes what comes back. It is clearly distinguishable from Bloomberg siblings like bloomberg_article, bloomberg_news and bloomberg_categories, which are article/news/category tools rather than profile lookups.

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 note that `<id>` is an opaque token that 'cannot be guessed' implies the URL must be sourced elsewhere (e.g. from an article byline), which is useful. However, it never explicitly says when to use this tool versus bloomberg_article or bloomberg_news, so routing is left to inference.

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