Adobe VIP Marketplace Docs MCP Server

Warm VIPMP docs cache

warm_vipmp_cache

Idempotent

Pre-fetch all documentation pages from the sitemap so searches match content, not just titles. First run takes ~30 seconds; later runs use cache for near-instant updates.

Instructions

Pre-fetch every page in the sitemap so subsequent searches can do content-level matching (not just title/tag matching).

First run takes ~30 seconds over ~70 pages. Subsequent runs are near-instant because the disk cache + ETag revalidation handle unchanged pages with 304 responses.

Returns a summary of fetches, cache hits, and any errors.

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": "warm_vipmp_cache"
  }
}

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

Behavior5/5

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

Annotations already indicate idempotence and non-destructiveness, and the description adds meaningful behavioral details: the ~30 second first-run duration, the near-instant subsequent runs, disk cache + ETag revalidation with 304 responses, and the returned summary. There is no contradiction with the 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, front-loaded with the core purpose, and every sentence contributes useful information. Timing, mechanism, and output summary are each given one focused sentence or short paragraph with no fluff.

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 zero-parameter, non-destructive, idempotent operation with an output schema, the description is complete. It covers purpose, expected duration, behavior on subsequent runs, and the nature of the return value, so an agent has enough to decide when and how to invoke it.

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 schema coverage is 100%, so there is nothing for the description to add about parameter meaning. The baseline of 4 is appropriate for a no-parameter tool.

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 states a specific action ('Pre-fetch every page in the sitemap') and a clear purpose ('so subsequent searches can do content-level matching'), which differentiates it from sibling tools like search or list operations. It is not a tautology and names the resource it acts on.

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 makes clear when to use the tool: before running searches that need content-level matching. It also sets expectations about first-run vs. subsequent-run cost, but it does not explicitly mention alternatives or conditions where this tool should not be used. Clear context, but no exclusions.

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