Skip to main content
Glama
xano-inc

Xano Developer MCP

Official
by xano-inc

xano_meta_api_docs

Read-onlyIdempotent

Retrieve documentation for Xano's Meta API to manage workspaces, databases, APIs, functions, and more programmatically.

Instructions

Get documentation for Xano's Meta API. Use this to understand how to programmatically manage Xano workspaces, databases, APIs, functions, agents, and more.

Topics

  • start: Xano Meta API - Getting Started

  • authentication: Authentication & Authorization

  • workspace: Workspace Management

  • apigroup: API Group Management

  • api: API Endpoint Management

  • table: Database Table Management

  • function: Reusable Function Management

  • task: Scheduled Task Management

  • agent: AI Agent Management

  • tool: Agent Tool Management

  • mcp_server: MCP Server Management

  • middleware: Middleware Management

  • branch: Branch Management

  • realtime: Realtime Channel Management

  • file: File Storage Management

  • history: Request & Execution History

  • workflows: Common Workflows

Usage

  • Start with "start" topic for overview and getting started

  • Use "workflows" for step-by-step guides

  • Use specific topics (workspace, table, api, etc.) for detailed endpoint docs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYesDocumentation topic to retrieve. Start with 'start' for an overview of the Meta API. Example: topic='workspace' for workspace management endpoints, topic='table' for database table operations.
detail_levelNoLevel of detail to return. 'overview' = brief summary of endpoints and their purpose. 'detailed' = full API reference with parameters, headers, and response formats. 'examples' = includes curl and fetch code examples for each endpoint. Default: 'detailed'.
include_schemasNoInclude JSON schemas for request bodies and response payloads. Useful for understanding the expected data format. Set to false to reduce response size. Default: true.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
documentationYesThe Meta API documentation content for the requested topic.
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description confirms read-only behavior by stating it 'gets documentation'. It adds context about available topics and response detail levels, but does not disclose additional behavioral traits beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with sections, bullet points, and usage tips. Every sentence serves a purpose, though it could be slightly more concise. Front-loaded with the main purpose.

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?

With 3 parameters fully documented in the schema, output schema present, and annotations covering safety, the description provides all necessary context: what the tool does, how to use it, and what topics are available. No gaps.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by recommending which topic to start with and explaining how to use each parameter (e.g., 'Start with "start" topic for overview'), enriching the schema's enum 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?

The description clearly states it retrieves documentation for Xano's Meta API, listing 17 specific topics and usage instructions. This clearly distinguishes it from sibling tools like xano_cli_docs which cover different APIs.

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?

Provides explicit guidance: start with 'start' topic, use 'workflows' for step-by-step guides, and pick specific topics (workspace, table, api, etc.) for detailed endpoint docs. Also implies when not to use (when other docs needed).

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/xano-inc/xano-developer-mcp'

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