Skip to main content
Glama
kuklaph
by kuklaph

Search Cascade

cascade_search
Read-onlyIdempotent

Search Cascade CMS assets by keywords, with optional field and type filters. Paginated results allow scoping to a specific site or across all sites.

Instructions

Search for assets across Cascade CMS by search terms, optional field subset, and asset type filter.

Runs a keyword search against Cascade's indexed content. Can be scoped to a single site (via siteId or siteName) or run across all sites when neither is provided. The searchFields array narrows which asset fields are matched (default: all searchable fields); searchTypes narrows which asset types are returned. Results are paginated client-side by this MCP layer.

Args:

  • searchInformation (object, required):

    • searchTerms (string, required): Keyword(s) to match, non-empty

    • siteId (string, optional): Restrict to a site by ID

    • siteName (string, optional): Restrict to a site by name (ignored if siteId is set)

    • searchFields (string[], optional): Fields to search. Allowed: "name", "path", "createdBy", "modifiedBy", "displayName", "title", "summary", "teaser", "keywords", "description", "author", "blob", "velocityFormatContent", "xml", "link". Default: all.

    • searchTypes (string[], optional): Asset types to return (e.g. ["page", "file"]). Default: all.

  • limit (number, optional): Max results per page, 1-500 (default 50)

  • offset (number, optional): Skip N results for pagination (default 0)

Returns: The response is a page: { success: true, total: , count: , offset: , has_more: , next_offset: <offset for next page, if has_more>, matches: [ { id, type, path: { path, siteId, siteName } }, ... ] } On failure: { success: false, message: "" }

Examples:

  • Use when: "Find all pages mentioning 'admissions'" -> { searchInformation: { searchTerms: "admissions", searchTypes: ["page"] } }

  • Use when: "Title search in site 'www'" -> { searchInformation: { searchTerms: "scholarship", siteName: "www", searchFields: ["title"] } }

  • Don't use when: You already know the id/path — use cascade_read directly.

  • Don't use when: You want audit events — use cascade_read_audits.

Pagination:

  • Default limit of 50 works for most queries. Increase up to 500 for larger pages.

  • If has_more is true and you need all results, call again with offset: next_offset.

  • For a complete enumeration (e.g., all pages matching a term), loop until has_more: false.

  • For focused searches where you only need top matches, stop as soon as you have what you need.

Error Handling:

  • "searchTerms must not be empty" when the term is missing or blank

  • "Site not found" when siteName/siteId is invalid

  • "Permission denied" when credentials lack read access. Responses are JSON text; structuredContent is authoritative when the response fits. Oversized responses return bounded _cache metadata for cascade_read_response. For cascade_read, read_mode controls preview versus raw Cascade payload shape.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchInformationNoSearch query and filters.
limitNoMaximum results per page (default: 50, max: 500). Check has_more and use next_offset to iterate. For a complete enumeration, loop until has_more=false.
offsetNoSkip this many results for pagination (default: 0). Use with limit + has_more to iterate through large result sets.
Behavior5/5

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

Annotations indicate readOnly, non-destructive, idempotent, open-world. The description adds pagination behavior (client-side, has_more, next_offset), error handling details, and notes on response format (JSON text, structuredContent, oversized responses). This adds significant context beyond 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?

The description is well-structured with sections (Args, Returns, Examples, Pagination, Error Handling). It is slightly lengthy but each part adds value; front-loaded purpose sentence. Loses a point for minor redundancy (some schema descriptions also present).

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?

Given the tool's complexity (multiple parameters, pagination, error cases), the description is thorough: covers pagination loop, error messages, examples, and return format. No output schema, but the description provides a clear return shape.

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?

Schema coverage is 100%, but the description provides rich parameter details: allowed values for searchFields, default behaviors for searchFields and searchTypes, and constraints (non-empty searchTerms). Examples further clarify parameter usage.

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 tool searches for assets across Cascade CMS by search terms, field subset, and asset type filter. It distinguishes itself from siblings like cascade_read (direct access by id/path) and cascade_read_audits (audit events), providing precise verb+resource+scope.

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?

The description includes explicit 'Use when' and 'Don't use when' examples, guiding the agent to use this tool for keyword searches and avoid it when the id/path is known (use cascade_read) or for audit events (use cascade_read_audits). It also explains scoping to a single site or all sites.

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/kuklaph/cascade-cms-mcp-server'

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