Skip to main content
Glama

export_project

Export an entire project workspace configuration (project metadata, collections, mock endpoints, webhooks, stateful config, and rules) as a portable, ID-stripped JSON document. Use this tool to create backups before destructive changes or to clone/migrate a project workspace via import_project.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "export_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesDatabase ID of the project workspace to export (obtain from list_projects).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / projectId / description
      Previous value: -"ID of the project to export"New value: +"Database ID of the project workspace to export (obtain from list_projects)."
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It does disclose a non-obvious trait — that identifiers are stripped, implying re-import creates new IDs — plus the scope of what is included. It does not state whether this is a purely read-only operation, whether any auth or plan restrictions apply, or whether large projects are truncated, which matters for a backup tool with zero annotation coverage.

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?

Two sentences, zero filler. The capability and its contents come first, and the usage/alternative routing comes second, which is the correct front-loading order.

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

Completeness4/5

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

For a one-parameter tool with no output schema, the description covers what an agent needs: what is exported, in what form, and why. The only shortfall is that with no output schema present, it could say slightly more about the returned document's structure or size characteristics.

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 description coverage is 100% and the single projectId parameter is already documented with its type and provenance (obtain from list_projects). The description adds no further meaning about that parameter, so the schema does all the work — baseline 3.

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?

States a specific verb (Export) and resource (entire project workspace configuration) and enumerates exactly what is captured: project metadata, collections, mock endpoints, webhooks, stateful config, and rules. The output form is named (portable, ID-stripped JSON), which cleanly separates it from siblings like get_project_context or list_mocks.

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?

Explicitly gives the two motivating scenarios: backups before destructive changes and clone/migrate workflows. It names the counterpart tool import_project as the mechanism for the migration path, so the agent knows both when to call this and what consumes its output.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources