Skip to main content
Glama
Sign In
appsmith-mcp

appsmith-mcp

by t0knight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_pages

Create multiple blank pages in the current Appsmith application by providing a list of page names in a single tool call.

Instructions

Create multiple blank pages in the current application in one tool call.

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": {
      "names": "<names>"
    },
    "name": "create_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions creating multiple blank pages but fails to describe side effects, error handling (e.g., duplicate names), or required permissions. Critical information is missing.

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

Conciseness3/5

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

The description is concise at 12 words, but it may be too brief, omitting necessary details. While front-loaded, it does not fully earn its place due to missing critical information.

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

Completeness2/5

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

Given the single parameter and no output schema, the description is incomplete. It does not explain return values, error behavior, or behavior for duplicate names. The agent lacks sufficient information to use the tool confidently.

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

Parameters1/5

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

The schema has 0% description coverage for the only parameter 'names', and the description adds no additional meaning beyond the schema. The agent has no information about what 'names' expects (e.g., uniqueness, format, constraints).

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 ('create'), the object ('blank pages'), and the context ('in the current application in one tool call'). It distinguishes from sibling tools like 'delete_pages' and 'list_pages' by specifying the creation of multiple pages.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. No mention of prerequisites, limitations, or when not to use it, which is essential for an AI agent to select the correct tool.

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

Deploy Server

Other Tools