Skip to main content
Glama

findTestimonials

Customer quotes for use in testimonials-block. author + quote required. Optional headline = one-line key statement shown above the quote — verbatim from the quote or approved by the customer, never invented. Rating 1-5. featured: true makes it prominent. rating = stars shown on THIS quote only; the site never derives an overall rating from quotes (no JSON-LD, no brand.json rating). Has drafts: use _status:"published" to go live (draft stays hidden); schedule a future date via the schedulePost tool (collection "testimonials"). testimonials collection. Drafts: yes (publish workflow; a find WITHOUT draft:true returns the published main-table state only). Public read: yes via /api/agents. MCP capabilities: find, create, update, delete. ⚠ delete is PERMANENT (hard-delete; the admin Trash does NOT catch MCP deletes). Write ONE document at a time: wait for the response of each create/update/delete call before sending the next — parallel writes can fail with a database deadlock (HTTP 500, nothing saved; retry that call alone). Before writing public text here, call getWritingGuidelines with this collection and the locale (brand voice, writing rules, fixed terms, SEO rules, taken keywords, field rules). Fields: author (required), role (localized), company, avatar (upload: media|brand), headline (localized), quote (textarea, localized, required), rating (number, 1–5), featured (boolean), publishedAt (date).

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": "findTestimonials"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoOptional: specific document ID to retrieve. If not provided, returns all documents
pageNoPage number for pagination (default: 1)
sortNoField to sort by (e.g., "createdAt", "-updatedAt" for descending)
depthNoHow many levels deep to populate relationships (default: 0)
draftNoOptional: Whether the document should be queried from the versions table/collection or not.
joinsNoOptional: configure join field queries, or pass false to disable all join fields.
limitNoMaximum number of documents to return (default: 10, max: 100)
trashNoOptional: include soft-deleted documents when trash is enabled on the collection
whereNoOptional JSON string for where clause filtering (e.g., '{"title": {"contains": "test"}}')
localeNoOptional: locale code to retrieve data in (e.g., "en", "es"). Use "all" to retrieve all locales for localized fields
selectNoOptional: define exactly which fields you'd like to return in the response, e.g., {"title": true}
populateNoOptional: control which fields to include from populated relationship or upload documents.
paginationNoOptional: set to false to skip the count query overhead
fallbackLocaleNoOptional: fallback locale code to use when requested locale is not available

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / joins
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": {},
      +      "type": "object"
      +    },
      +    {
      +      "const": false,
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Optional: configure join field queries, or pass false to disable all join fields."
      +}
    • addedInput schema / properties / pagination
      Added value: +{
      +  "description": "Optional: set to false to skip the count query overhead",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / populate
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Optional: control which fields to include from populated relationship or upload documents.",
      +  "type": "object"
      +}
    • addedInput schema / properties / select / additionalProperties
      Added value: +{}
    • changedInput schema / properties / select / description
      Previous value: -"Optional: define exactly which fields you'd like to return in the response (JSON), e.g., '{\"title\": true}'"New value: +"Optional: define exactly which fields you'd like to return in the response, e.g., {\"title\": true}"
    • changedInput schema / properties / select / type
      Previous value: -"string"New value: +"object"
    • addedInput schema / properties / trash
      Added value: +{
      +  "description": "Optional: include soft-deleted documents when trash is enabled on the collection",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so unusually well: it discloses the draft/publish workflow (a find WITHOUT draft:true returns published main-table state only), public read exposure via /api/agents, that delete is a permanent hard-delete bypassing the admin Trash, and that parallel writes can deadlock with HTTP 500 and nothing saved. It also preempts a real misinterpretation by stating the site never derives an overall rating from quotes (no JSON-LD, no brand.json rating).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense and information-rich, but poorly front-loaded: the opening clause defines what a testimonial contains rather than what the tool does, and most of the middle is write-side field and workflow guidance irrelevant to invoking a find. The genuinely read-relevant facts (draft behavior, public read, locale) are scattered rather than grouped, so an agent must read the whole block to extract the two or three sentences that matter here.

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?

For a 14-parameter, no-output-schema collection query, the definition covers collection identity, draft/published visibility, locale handling, public read surface, and the prerequisite guideline call. It omits how the paginated response is shaped and what `where`/`joins`/`populate` do at runtime beyond the schema's own wording, which is a reasonable gap given a 100%-covered schema.

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 already 100%, so the baseline is 3, and the description adds genuine meaning on top: `draft` is explained in terms of which table state is returned, `_status` values are given for publishing, and `rating` is scoped to this quote only rather than an aggregate. Field-level notes (role/headline/quote are localized, avatar takes a media|brand upload) also add beyond the schema's type declarations, though pagination/sort/where semantics are left entirely to the schema.

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 first sentence identifies the specific resource ('Customer quotes for use in testimonials-block') and the name supplies the verb, so an agent can tell this apart from findPosts/findFaqs without opening the schema. However, the line 'MCP capabilities: find, create, update, delete' muddies the purpose of a tool named find — it never plainly says 'retrieves testimonial documents', leaving the agent to infer the read operation from the tool name rather than the description.

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 conditional guidance: use `_status:"published"` to go live, schedule via the schedulePost tool for collection 'testimonials', call getWritingGuidelines before writing public text, and wait for each write response before the next. What it lacks is read-side routing — no statement of when to use this collection query versus a general search, and no exclusion for the write-oriented siblings it alludes to.

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