Skip to main content
Glama

search

Full-text search across every page on momenticmarketing.com (blog posts, research, the Google update tracker with each update's status and dates, case studies, Content Academy guides, Atlas, team pages, careers, the SEO news feed item by item, and Momentic's agent tools and skills), including pages published since Webflow's sitemap was last rebuilt. Returns up to 10 pages ranked by relevance (newest first when the query asks for the latest, newest or most recent; tracker pages by the date Google announced the update), each with its URL, title, content type, published date, author and the passage that best matches the query. Read a full page with get_page.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOptional: only pages of this content type.
queryYesSearch term or question
formatNoOptional: json returns structured results (url, title, type, date, author, image, passage; tracker pages also tracker: status, announced, started, completed, kind).
recentNoOptional: newest first among relevant pages (also implied by words like latest, newest, most recent in the query). Tracker pages sort by the date Google announced the update.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / format
      Added value: +{
      +  "description": "Optional: json returns structured results (url, title, type, date, author, image, passage; tracker pages also tracker: status, announced, started, completed, kind).",
      +  "enum": [
      +    "text",
      +    "json"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Search term"New value: +"Search term or question"
    • addedInput schema / properties / recent
      Added value: +{
      +  "description": "Optional: newest first among relevant pages (also implied by words like latest, newest, most recent in the query). Tracker pages sort by the date Google announced the update.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / type
      Added value: +{
      +  "description": "Optional: only pages of this content type.",
      +  "enum": [
      +    "research",
      +    "blog",
      +    "google-update",
      +    "case-study",
      +    "guide",
      +    "atlas",
      +    "event",
      +    "team",
      +    "service",
      +    "news",
      +    "agent",
      +    "page"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the result cap (up to 10), relevance ranking, the newest-first ordering rule and its trigger words, the tracker-specific sort by Google announcement date, the per-result fields, and the important index-coverage caveat that pages published after Webflow's sitemap rebuild are included. It omits failure/empty-result behavior and whether queries are free-text or fielded, which keeps it short of a 5.

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?

Front-loads the core purpose, then ordering behavior and the get_page handoff. The long parenthetical inventory of content types is dense but earns its place by defining the index scope; the sentence could still be trimmed without loss.

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?

There is no output schema, so the description must describe returns — and it does, listing URL, title, content type, published date, author and best-matching passage. Combined with ordering rules, result limits, and the get_page escape hatch, an agent has everything needed to call and consume this tool correctly.

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?

Schema coverage is 100%, so a 3 is the floor; the description goes beyond it by explaining that `recent` is implied by words like latest/newest/most recent, that tracker pages sort by Google's announcement date, and that `format=json` returns structured fields including tracker status/announced/started/completed/kind. The `type` enum values are already fully documented in the schema, so the marginal gain is modest rather than maximal.

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+resource ('Full-text search across every page on momenticmarketing.com') and enumerates the indexed content types, so the agent knows exactly what corpus is covered. It also differentiates itself from the sibling get_page by routing the agent there for full-page reads.

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?

Gives clear context (search when you need ranked, passage-level matches across the site) and names the follow-up alternative ('Read a full page with get_page'). It does not, however, address when to prefer list_pages or lookup_entity over search, so exclusions are incomplete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources