Skip to main content
Glama

retrieve_page

Retrieve a page from Plane using its page ID. Optionally include a project ID to fetch a project page; otherwise, it returns a workspace page.

Instructions

Retrieve a page by ID.

Retrieves a project page if project_id is given, otherwise a workspace page.

Args: page_id: UUID of the page project_id: UUID of the project. Omit for a workspace page.

Returns: Page object

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYes
project_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameNo
anchorNo
owned_byNo
projectsNo
workspaceNo
created_atNo
updated_atNo
descriptionNo
description_htmlNo
description_binaryNo
description_strippedNo
Behavior3/5

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

With no annotations, the description carries the burden. It indicates a read operation via 'retrieve' and explains the conditional behavior and return type, but it does not disclose error handling, permissions, or side effects.

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?

The description is concise and well-structured with an opening purpose statement followed by Args and Returns sections. Every sentence adds value without redundancy.

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?

Given the simple 2-parameter retrieval tool with an output schema present, the description covers all necessary aspects: scope selection, parameters, and return type. It is complete for correct selection and invocation.

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

Parameters5/5

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

Schema has 0% description coverage, but the description fully compensates by explaining the meaning of both parameters, their types (UUID), and the conditional omission of project_id for workspace pages.

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 the action ('Retrieve a page by ID') and specifies the scope distinction between project and workspace pages, which differentiates it from sibling tools like list_pages and other retrieve_* tools.

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?

It provides clear usage context by explaining when project_id should be given vs omitted, effectively guiding agent behavior. However, it does not explicitly mention alternatives or when not to use this tool.

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/leigangzhang/plane-mcp-server-adapter'

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