Xbitto MCP

Overview Schema Source Related Servers Discussions Admin

List Vault

list_vault

Read-only

Retrieve a creator account's Vault items (galleries, videos, series), newest first, ten per page, with cursor-based pagination.

Instructions

The account's Vault items (galleries, videos, series), newest first, ten a page.

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_vault"
  }
}

Input Schema

Name	Required	Description	Default
`cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 21, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description goes beyond that by disclosing result ordering ('newest first') and page size ('ten a page'), both of which change agent behavior (it must loop). It does not mention auth scope beyond 'the account's' or any rate limits, so it is strong but not exhaustive.

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?

A single front-loaded sentence naming resource, contents, ordering, and page size with zero filler. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does describe the returned item types and ordering, which is helpful. However the cursor parameter is undocumented in both schema and description, leaving the agent without the information needed to actually paginate. Adequate but with a concrete gap.

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

Parameters3/5

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

Schema coverage is 0% for the single optional cursor parameter, so the description must compensate. 'Ten a page' implies pagination and thus a cursor, but the description never explains what the cursor is, where it comes from, or how to advance pages. Partial compensation, baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (list) and resource (the account's Vault items) and enumerates the item subtypes it returns (galleries, videos, series), which clearly separates it from the singular get_vault_item sibling. It stops short of explicitly naming that sibling as the alternative, so it is clear but not fully differentiated in prose.

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?

There is no when-to-use or when-not-to-use statement and no named alternative. Usage is only implied: the tool is obviously for browsing the account's Vault, and 'ten a page' signals the agent should be prepared to page. That is adequate but leaves the agent to infer the split with get_vault_item.

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