Adobe VIP Marketplace Docs MCP Server

List VIPMP docs sitemap

list_vipmp_docs

Read-onlyIdempotent

Browse the full Adobe VIP Marketplace API documentation sitemap to discover all available topics and locate exact page paths.

Instructions

Return the full sitemap of Adobe VIP Marketplace API documentation. Use this to browse all available topics or to find exact page paths.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_vipmp_docs"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.17.0Sep 1, 2026
Removedv0.13.1Jul 27, 2026
First observedv0.9.0Jun 24, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the result is the full sitemap and can be used for browsing or path discovery, but says little about output size, pagination, or other operational behavior. This is adequate but not rich.

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 two sentences with no filler. The key action (returning the full sitemap) is front-loaded, and the follow-up sentence adds immediate practical use.

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?

This is a zero-parameter, read-only tool with an output schema, so the description fully covers what an agent needs to select and invoke it correctly. The purpose and use cases are stated clearly, and no additional prerequisites or edge-case warnings are needed.

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 tool has zero parameters and the schema has 100% coverage, so parameter documentation is unnecessary. The baseline of 4 applies because no parameter semantics are needed.

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?

The description clearly states the tool returns the full sitemap of Adobe VIP Marketplace API documentation, which is a specific resource and action. This distinguishes it from search_vipmp_docs, get_vipmp_page, and list_vipmp_endpoints by emphasizing the complete sitemap rather than individual pages or endpoint details.

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?

The description provides a clear use case: browse all topics or find exact page paths. It does not explicitly name alternatives or say when not to use this tool, but the stated purpose is enough to guide selection among the siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.