Skip to main content
Glama

create_page

Create a page within a Plane project or workspace by providing a name and HTML content; optionally configure access, color, and other settings.

Instructions

Create a page.

Creates a project page if project_id is given, otherwise a workspace-level page.

Args: name: Page name description_html: Page content in HTML format project_id: UUID of the project. Omit to create a workspace page. access: Access level for the page (integer) color: Page color is_locked: Whether the page is locked archived_at: Archive timestamp (ISO 8601 format) view_props: View properties dictionary logo_props: Logo properties dictionary external_id: External system identifier external_source: External system source name

Returns: Created Page object

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
colorNo
accessNo
is_lockedNo
logo_propsNo
project_idNo
view_propsNo
archived_atNo
external_idNo
external_sourceNo
description_htmlYes

Output Schema

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

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

Annotations already indicate write (readOnlyHint=false) and non-destructive (destructiveHint=false). Description adds behavioral details about page location and lists all parameters, adding context 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.

Conciseness4/5

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

Well-structured with a clear first line and a bullet-like parameter list. Slightly verbose but each sentence adds value; could be tightened without losing clarity.

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?

Given 11 parameters and an output schema mentioned, the description covers the main behavior and parameter purposes. Does not detail return format, but output schema is present. Adequate for an agent to invoke correctly.

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?

With 0% schema description coverage, the description provides essential meaning for all 11 parameters (e.g., 'Project name', 'Page content in HTML format', 'UUID of the project. Omit to create a workspace page.'), making it highly informative beyond the bare 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?

Description clearly identifies the action ('Create a page') and distinguishes between creating a project page or workspace-level page based on project_id. This differentiates from sibling tools like update_page or delete_page.

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 clear context: include project_id for a project page, omit for workspace page. Does not explicitly state when not to use or list alternatives, but the guidance is sufficient for an agent to decide.

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/Bl4nk44/plane-ce-mcp'

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