Skip to main content
Glama
softwareone-platform

Adobe VIP Marketplace Docs MCP Server

List VIPMP release notes

list_vipmp_releases
Read-onlyIdempotent

List VIPMP releases filtered by date and section. Each entry includes changes for API, sandbox, upcoming, and earlier releases.

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
NameRequiredDescriptionDefault
sinceNo
sectionNo
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds that data is from a pre-built index (fast, daily refreshed) and clarifies exclusion behavior for `since`. No contradictions.

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?

Well-organized with overview, parameter docs, and examples. Every sentence adds value; no redundancy. Length appropriate for describing a filtered list tool with 3 parameters.

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?

Covers all aspects: data source, filtering, parameter details, and examples. With an output schema present, return values need no explanation. Complete for a list-release tool with good annotations.

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?

Though schema coverage is 0%, the description fully documents each parameter: `since` format and exclusions, `section` enum meanings, `limit` default. Provides examples for each. Compensates completely for lack of schema descriptions.

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?

Explicitly states it returns structured VIPMP release notes, describes data structure (date, section, changes), and differentiates from siblings like list_vipmp_docs and list_vipmp_endpoints by focusing on release notes.

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?

Provides clear examples for typical use cases (since, section, limit) and explains the effect of each parameter. Could explicitly compare to search_vipmp_docs for broader search, but examples cover main usage patterns.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/softwareone-platform/swo-adobe-vipm-docs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server