Adobe VIP Marketplace Docs MCP Server

Clear VIPMP docs cache

vipmp_cache_clear

DestructiveIdempotent

Clears cached documentation entries to reflect updates. Specify a path to invalidate one entry, or clear the entire cache by omitting it.

Instructions

Clear the docs cache. Pass a specific doc path to invalidate one entry, or omit to wipe the entire cache.

Args: path: Optional docs path to invalidate (e.g. "/vipmp/docs/lga/create/"). If None, clears everything.

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

Input Schema

Name	Required	Description	Default
`path`	No

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 operation destructive and idempotent. The description adds meaningful scope details: invalidating a single entry vs wiping the entire cache, and the fact that omitting the path clears everything. It does not contradict any annotation and gives enough behavioral framing around the destructive scope.

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, with the core behavior stated in the first sentence. The parameter documentation is minimal and directly useful, containing every necessary detail with no filler.

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 single-parameter cache-clearing tool with destructive and idempotent annotations and an output schema present, the description provides everything needed to invoke it correctly. The two possible behaviors are fully specified, and the output schema removes the need to describe return values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema is sparse (single nullable string, 0% coverage), but the description fully compensates. It explains what 'path' means, gives a concrete example, and explicitly states the effect of None (clearing everything). This is exactly the compensation needed for a minimally documented parameter.

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 action ('Clear the docs cache') and the exact two operating modes: invalidate a specific path or wipe the entire cache. This distinguishes it from sibling cache-related tools like warm_vipmp_cache and vipmp_cache_stats without needing to inspect their schemas.

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?

It gives clear guidance on when to pass a path versus omitting it, which is the main invocation decision. However, it never references sibling tools or explains when clearing is preferable to warming, refreshing, or rebuilding the cache, leaving context-based selection to inference.

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