Adobe VIP Marketplace Docs MCP Server

by softwareone-platform

Overview Schema Source Related Servers Score Discussions Admin

Python

Local

List VIPMP release notes

list_vipmp_releases

Read-onlyIdempotent

Retrieve structured Adobe VIP Marketplace release notes, filtered by date or section, to track API and sandbox changes.

Instructions

Return structured VIPMP release notes — the highest-signal information for developers tracking API changes. Served from the pre-built index (refreshed daily), so calls return in milliseconds.

Each entry has a date, a section ("api_changes", "sandbox", "upcoming", or "earlier"), and one or more changes with titles and bodies. Covers both the main API changes and the Sandbox-specific changes at the bottom of the release-notes page — they're tracked separately.

Args: since: ISO date ("YYYY-MM-DD"). If provided, returns only releases on or after this date. Example: "2026-01-01" for everything since New Year. Entries without a date (catch-all "earlier releases" buckets) are excluded when since is set. section: Optional filter. One of: - "api_changes" — the main API release stream - "sandbox" — Sandbox-environment-specific changes - "upcoming" — announced but not yet shipped - "earlier" — catch-all entries without a specific date limit: Maximum number of release entries to return (default 20).

Examples: # What shipped in 2026? list_vipmp_releases(since="2026-01-01", section="api_changes")

# Recent sandbox-only changes
list_vipmp_releases(section="sandbox", limit=5)

# What's coming
list_vipmp_releases(section="upcoming")

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`since`	No
`section`	No

Output Schema

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

Behavior5/5

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

Annotations already mark this read-only, idempotent, and non-destructive. The description adds valuable behavioral context beyond that: responses are served from a pre-built daily-refreshed index for millisecond latency, API and Sandbox changes are tracked separately, and `since` excludes undated 'earlier' entries. No contradiction with 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 long but tightly organized: purpose first, return-structure summary, then Args and Examples. Every sentence adds value — the latency note, the separate-streams note, and the example calls all earn their place. The structure makes it easy for an agent to parse.

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 read-only listing tool with an output schema present, this description covers all the ground: what is returned, how data is sourced, how filtering behaves, parameter semantics, and common usage patterns. Nothing an agent needs to select and call this tool correctly is missing.

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?

Schema description coverage is 0%, so the description carries the full burden for parameter meaning — and it delivers. Each of the three parameters gets precise semantics: `since` includes format, behavior, and example; `section` enumerates all four values with meanings; `limit` gets its default. This far exceeds the bare 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?

The description opens with 'Return structured VIPMP release notes' — a specific verb, resource, and clearly stated value proposition for developers tracking API changes. It also distinguishes this tool from the many sibling doc tools by explicitly scoping it to release notes and mentioning both API and Sandbox streams.

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 gives clear context for when to use the tool ('developers tracking API changes'), explains what each section filter means, and provides practical examples for common use cases. It doesn't explicitly name sibling alternatives or say when not to use it, which keeps it just short of a 5.

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