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 programmatically manage workspaces, databases, APIs, functions, agents, and more. Begin with the 'start' topic for an overview.

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 indicate readOnly, non-destructive, and idempotent. The description adds value by explaining the retrieval of documentation and the organizational structure of topics, without contradicting 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?

Front-loaded with purpose, uses clear section headings (Topics, Usage), and every sentence adds value. No wasted words given the number of topics listed.

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 a clear input schema, existing output schema, and thorough topic list, the description fully covers what the tool does and how to use it for documentation retrieval. No missing context.

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 100% with descriptions for all three parameters. The description adds context by listing topics and usage patterns, but doesn't significantly enhance parameter understanding beyond 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 clearly states 'Get documentation for Xano's Meta API,' a specific verb-resource combination. It distinguishes from sibling tools like CLI, validation, and XanoScript docs by focusing on the Meta API, and lists covered topics.

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 explicit guidance: start with 'start', use 'workflows' for step-by-step, specific topics for detailed docs. While it doesn't explicitly state when not to use, the context is clear and includes recommendations.

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