Skip to main content
Glama
Sign In
appsmith-mcp

appsmith-mcp

by t0knight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_pages

List all pages in the current Appsmith application, showing id, name, default/hidden flags, and the active page.

Instructions

List all pages in the current application with id, name, default/hidden flags, and which is currently active.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It describes what the tool does (list with fields) but doesn't disclose any behavioral traits like read-only nature, performance implications, or that it's safe to call multiple times. For a simple list, this is adequate but minimal.

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?

Single sentence, well-structured, front-loaded with key information. No wasted words.

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?

For a zero-parameter list tool with no output schema, the description fully covers what the tool does and what it returns (id, name, flags, active page). No gaps given complexity level.

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

Parameters4/5

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

Input schema has no parameters (100% schema coverage trivially). Description adds no parameter info because none needed. Baseline of 4 is appropriate as description is not required to add meaning beyond schema for 0-param tools.

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 states the verb 'List' and the resource 'pages in the current application', with explicit fields returned. No ambiguity and distinct from sibling tools like list_apps or list_datasources.

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?

Implicit usage context is clear (list all pages), but no explicit guidance on when to use this vs alternatives or any exclusions. For a simple list operation this is sufficient, but could be improved by noting it returns all pages without filtering.

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