Adobe VIP Marketplace Docs MCP Server

List VIPMP tip topics

list_vipmp_tip_topics

Read-onlyIdempotent

Discover which SoftwareOne tip topics are available for Adobe VIP Marketplace. Use the resulting topic names to retrieve details for a specific tip.

Instructions

Return the list of topics for which SoftwareOne tips are available.

Each entry maps to an H2 section in the tips file; call get_vipmp_tips(topic) to read one. Useful as a discovery call — "what tips do you have?" — before narrowing to a specific topic.

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

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

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by explaining that entries map to H2 sections in the tips file, which tells the agent how the list relates to the file structure and the subsequent call.

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?

Three sentences, with the primary purpose front-loaded and each subsequent sentence adding meaningful navigation or usage context. No filler or repetition of schema/annotation data.

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?

This is a simple, parameterless listing tool with rich annotations and an output schema. The description fully covers what the tool returns, how entries map to the tips file, and how the tool fits into the workflow with `get_vipmp_tips`.

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, so there is nothing for the description to clarify. Schema coverage is effectively 100% since the input schema is empty, and the parameter-less baseline of 4 applies.

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 verb and resource: "Return the list of topics for which SoftwareOne tips are available." It further clarifies that each entry maps to an H2 section and is linked to `get_vipmp_tips(topic)`, distinguishing it from sibling listing tools like `list_vipmp_docs`.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly frames this as a discovery call — "what tips do you have?" — before narrowing to a specific topic, and directs the agent to `get_vipmp_tips(topic)` as the follow-up. This is clear when-to-use guidance with an explicit alternative.

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