Skip to main content
Glama
Sign In
mapbox-docs

mapbox-docs

Official
by mapbox
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Batch Get Mapbox Documents Tool

batch_get_documents_tool
Read-onlyIdempotent

Fetch the full content of up to 20 Mapbox documentation pages in one call and return per-page errors without failing the entire batch.

Instructions

Fetch the full content of multiple Mapbox documentation pages in a single call (max 20). More efficient than calling get_document_tool multiple times. Returns an array of results — failed pages include an error message rather than failing the whole batch.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "urls": "<urls>"
    },
    "name": "batch_get_documents_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesArray of Mapbox documentation page URLs to fetch (max 20). All must be https://docs.mapbox.com URLs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / urls / description
      Previous value: -"Array of Mapbox documentation page URLs to fetch (max 20). All must be mapbox.com URLs."New value: +"Array of Mapbox documentation page URLs to fetch (max 20). All must be https://docs.mapbox.com URLs."
  2. First observedv0.3.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond them: the 20-item ceiling and, most importantly, partial-failure semantics — failed pages return an error entry rather than aborting the whole batch. It could go further on content size or truncation, but this is solid added context.

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?

Three short sentences, each earning its place: capability, alternative routing, then failure behavior. The limit is front-loaded and there is no filler.

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?

There is no output schema, so the description usefully explains the return shape (an array of results with per-item error messages). That covers the main ambiguity for a batch tool. It stops short of describing result ordering, item field structure, or how large the returned page content may be.

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 coverage is 100% and the single parameter already documents the array type, maxItems 20, and the https://docs.mapbox.com URL constraint. The description only restates the max-20 limit and says 'full content' without adding format or syntax detail. Baseline 3 is correct when the schema carries this much.

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 ('Fetch the full content of multiple Mapbox documentation pages') plus the batch scope ('in a single call (max 20)'). It explicitly names the sibling get_document_tool as the non-batch equivalent, so an agent can distinguish it without opening either schema.

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

Usage Guidelines4/5

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

Gives clear selection logic: use this instead of 'calling get_document_tool multiple times'. The max-20 cap implicitly frames the batch case. It does not address the other sibling search_mapbox_docs_tool or state when a single-page fetch is preferred, so it falls just short of explicit when/when-not routing.

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