Adobe VIP Marketplace Docs MCP Server

Describe VIPMP endpoint

describe_vipmp_endpoint

Read-onlyIdempotent

Fetch Adobe VIPMP endpoint details in one call: schema, error codes, code examples, and release notes. Eliminates the need for multiple separate lookups.

Instructions

One-shot profile of a VIPMP endpoint. Returns schema, error codes, code examples, and any release-note mentions in one call — so Claude doesn't have to chain 4 separate tool invocations.

Args: method: HTTP method (GET / POST / PATCH / PUT / DELETE). path: API path (e.g. "/v3/customers").

Example: describe_vipmp_endpoint(method="POST", path="/v3/customers")

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": {
      "method": "<method>",
      "path": "<path>"
    },
    "name": "describe_vipmp_endpoint"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`method`	Yes

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.4/5.0

Behavior4/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive, and the description is consistent with that, adding that it aggregates several data categories into one call. It does not mention caching or freshness, but the safety profile is already covered by annotations.

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 compact and front-loaded: a one-sentence value proposition, per-argument definitions, and a single example. It avoids restating schema fields or annotations and every sentence contributes to correct selection and invocation.

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?

Given the output schema and read-only/idempotent annotations, the description sufficiently explains what the tool aggregates, why it exists, and how to call it. An explicit sibling-routing condition would be a small enhancement, but nothing critical is missing.

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 description coverage is 0%, so the Args block carries the documentation burden. It defines method as an HTTP verb with the allowed values, path with a concrete example, and includes a full invocation example, though it does not add constraints beyond the schema.

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 it produces a one-shot endpoint profile composed of schema, error codes, code examples, and release-note mentions. This makes it clearly distinguishable from the granular get/list sibling tools such as get_vipmp_schema, list_vipmp_error_codes, and get_vipmp_code_examples.

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 frames the tool as the alternative to chaining four separate tool invocations, which gives a clear when-to-use rationale. It stops short of naming the specific sibling tools or stating when a narrower sibling should be used instead.

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