Skip to main content
Glama
fruggr

Zendesk MCP Server by Fruggr

by fruggr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search Help Center Articles

search_articles
Read-onlyIdempotent

Search Zendesk Help Center article metadata by full-text query, filter by locale, and paginate results; returns total count to locate relevant articles without loading full bodies.

Instructions

Full-text search across Help Center articles (metadata only, no body). Use get_article for full content. Supports locale filtering. Returns total count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number for offset pagination. Increment it while keeping `per_page` fixed to fetch subsequent pages; page 1 is the first page.
queryYesFull-text query matched against article titles and body. Plain keywords; combine with the locale filter to scope to one language.
localeNoFilter by locale (e.g., "en-us", "fr")
per_pageNoNumber of results per page for offset pagination (1-100). Pair with `page` to walk large result sets; the response header reports the total count and whether more pages remain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.24.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed3 schema fields changedv2.6.0
    • changedInput schema / properties / page / description
      Previous value: -"Page number"New value: +"1-based page number for offset pagination. Increment it while keeping `per_page` fixed to fetch subsequent pages; page 1 is the first page."
    • changedInput schema / properties / per_page / description
      Previous value: -"Results per page"New value: +"Number of results per page for offset pagination (1-100). Pair with `page` to walk large result sets; the response header reports the total count and whether more pages remain."
    • changedInput schema / properties / query / description
      Previous value: -"Search query"New value: +"Full-text query matched against article titles and body. Plain keywords; combine with the locale filter to scope to one language."
  3. Changed1 schema field changedv2.3.1
    • addedInput schema / additionalProperties
      Added value: +false
  4. First observedv1.7.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely useful context not in the annotations: results are metadata only and exclude article bodies, and the response reports a total count. It does not disclose ranking behavior or empty-result handling, so it is solid but not rich.

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?

Three short sentences with zero filler; the scope constraint (metadata only) and the alternative tool are front-loaded before secondary details like locale and count.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully states that a total count is returned, and annotations carry the safety profile. Pagination and query semantics live in the schema. What is missing is only marginal – ranking/relevance behavior and how results are ordered.

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% – each of the four parameters is documented in the schema, including pagination mechanics. The description only echoes locale filtering, which the schema already explains, so a baseline 3 is appropriate.

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 ('Full-text search across Help Center articles') with an explicit scope qualifier ('metadata only, no body'). It also names the sibling tool that serves the complementary need (get_article), so an agent can distinguish it without opening either schema.

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?

Explicitly routes the agent to get_article when full content is needed, and notes locale filtering is supported. However, it gives no guidance on when to prefer this over list_articles/list_sections or other sibling listing tools, so the exclusion set is partial.

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