Skip to main content
Glama
Sign In
msloop-mcp

msloop-mcp

by shayanline
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

loop_list_pages

Lists all pages in a specified Microsoft Loop workspace using the workspace ID. Optionally includes deleted pages.

Instructions

List the pages in a Loop workspace. Pass the workspace id from loop_list_workspaces.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "loop_list_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesThe workspace id to list pages for.
include_deletedNoInclude deleted pages. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description should disclose behavior. It only states it lists pages, omitting details about pagination, rate limits, or any destructive potential. The include_deleted parameter hints at a default behavior but is not described in the description.

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?

Two sentences front-load the purpose and provide a practical hint. No fluff, but could be slightly more structured with separate usage guidance.

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?

As a list tool with no output schema, the description should explain the return format (e.g., list of page titles/IDs). It lacks details on pagination, error conditions, or the effect of include_deleted. This leaves the agent guessing.

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 coverage is 100% with descriptions for both parameters. The description adds value by suggesting the workspace_id come from loop_list_workspaces, but does not elaborate on include_deleted beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'List the pages in a Loop workspace' with a specific verb and resource. It also provides a hint to use the workspace id from loop_list_workspaces, helping to distinguish from sibling tools like loop_get_page or loop_search.

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

Usage Guidelines3/5

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

The description implies usage context by referencing loop_list_workspaces, but does not explicitly state when to use this tool versus alternatives (e.g., loop_search) or provide exclusions.

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