Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

List block usage

list_block_usage
Read-only

Report where each block type is stored across draft, published, layout, and developer surfaces, with counts, pages, and orphan or unused status to guide migration or removal before code changes.

Instructions

Show where each block type is stored across the workspace: draft and published page blocks, layout regions (draft and published) and developer drafts, with per-surface counts and the pages that hold it. registered says whether the active block manifest still declares the type; orphanTypes lists types stored but no longer registered (the site renders nothing for them), unusedTypes lists registered types no page uses. Use it before renaming or removing a block type in code, then migrate or remove the instances it lists with update_block_content / remove_block_from_page.

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_block_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
typesNoOnly report these block types. Omit to report every type the workspace stores or registers.
includeHistoryNoAlso count the page version history, including versions of deleted pages. Off by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.73.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds real behavioral context by explaining that orphan types render nothing on the site, that unused types are registered but unreferenced, and what `registered` reflects against the active manifest. With no output schema, this return-field explanation carries useful weight, though it could note result size or pagination behavior.

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?

Information-dense and front-loaded: the scope statement comes first, followed by field definitions and then next steps. Some sentences are long with stacked clauses, but nothing is redundant.

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 read-only inspection tool with a fully documented two-parameter schema, the description covers what surfaces are reported, how to interpret the special type buckets, and what to do next — nothing an agent needs to invoke it correctly is missing.

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 description coverage is 100% and both parameters (types, includeHistory) are documented in the schema, so the baseline of 3 applies; the description adds no extra meaning such as matching semantics or case sensitivity for the type strings.

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?

States a specific verb and resource ("Show where each block type is stored across the workspace") and enumerates the surfaces covered, so an agent can distinguish it from list_block_types, which deals with the manifest rather than storage locations.

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

Usage Guidelines5/5

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

Gives an explicit precondition ("Use it before renaming or removing a block type in code") and names the follow-up tools (update_block_content / remove_block_from_page) that act on the instances it reports, establishing a clear workflow position among siblings.

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