Skip to main content
Glama

findTeam

Team members / people (Person profiles). A person gets a public author page /team/ once they have at least one published post (authorMode: "person" + teamAuthor); its URL is canonicalUrl in the response. slug is always generated from name (read-only, localized); there is deliberately NO index page /team (a team overview, if any, is a regular page). The author page shows photo, role, bio and the person's published posts automatically. name is required (language-neutral); role/department/bio/quote/qualifications are localized. socialLinks + languages are one-per-line textareas (→ Person sameAs / knowsLanguage). email/phone are public when filled. photo is an upload. Manual order via order (team block, not the author page). Site-specific profile fields: knowsAbout (see the field descriptions; shown on the author page and in its Person markup). Linked to the site Organization (worksFor) in JSON-LD; referenced as a post author — use the find tool to list members with their id (needed for a post's authorMode: "person" + teamAuthor + getPersona(<id>)), which makes the post byline link to the author page and its author point at the person's profile node. Never set a person as author without evidence they wrote the post (default: organization). style (the writing voice) is REDACTED in find responses — read the real value via getPersona(<id>). team 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: name (required), slug (localized), role (localized), bio (richText, localized), quote (textarea, localized), photo (upload: media|brand), order (number), kind (enum: member (Team member (shown + author))|display (Display only (shown, not author))|author (Author only / guest (not shown)), required), department (localized), email, phone, socialLinks (textarea), qualifications (textarea, localized), languages (textarea), knowsAbout (textarea, localized), style (textarea, localized, redacted), publishedAt (date), robots (enum: index (Index (default))|noindex (noindex (hide))), searchText (textarea, localized, ≤60000 chars, redacted), meta (group: title, description, focusKeyword, secondaryKeyword1-4, searchIntent, eeatInsight, image — localized).

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

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

B3/5.0
Behavior3/5

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

With no annotations, the description does carry real behavioral detail: `style` and `searchText` are redacted in find responses, drafts require draft:true, data is publicly readable via /api/agents, slug is read-only and generated from `name`, and localized fields vary by locale. However, it also advertises "MCP capabilities: find, create, update, delete", permanent hard-delete semantics, and write-deadlock warnings for a tool whose schema is a pure read/list query — behavior that this tool cannot exhibit. That misdirection dilutes otherwise strong disclosure.

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

Conciseness2/5

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

It is a single dense paragraph of CMS/data-model documentation with no front-loaded statement of the operation, no sentence breaks, and heavy parenthetical notation. Sections on JSON-LD Organization links, author-page rendering, and write-safety are large and mostly irrelevant to invoking a find call. Content that does matter (draft, locale, redaction) is not prioritized.

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 find with full schema coverage, the definition does cover the non-obvious risks an agent needs: redacted fields, draft vs published state, locale handling, and public readability. It is missing a clear statement of return shape, pagination defaults, and how `where`/`select`/`joins` behave in this collection, but with no output schema and a well-documented schema, this is close to sufficient.

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 the baseline is 3, and the description genuinely adds meaning on top: it explains that a query without draft:true returns only published main-table state, and that name is language-neutral while role/department/bio/quote/qualifications are localized — which directly informs how to use the `locale`/`fallbackLocale` params. It also warns that `style` and redacted fields come back masked, which affects `select` decisions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with "Team members / people (Person profiles)" — a resource label, not a verb+resource statement. Nothing in the first sentence says this tool retrieves or lists team members; the reader has to infer the find behavior from the schema and the name. The bulk of the text describes the Person data model (author pages, JSON-LD, localized fields) rather than what the call does, and there is no differentiation from siblings like findPages or findPosts beyond the collection name.

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

Usage Guidelines2/5

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

There is no statement of when to call findTeam versus the other find* tools in the catalog. The only routing advice — "use the `find` tool to list members with their `id`" — points at a tool that isn't in the sibling list, and is self-referential given this tool is itself named findTeam. Useful fragments exist ("a find WITHOUT draft:true returns the published main-table state only", read `style` via getPersona), but they are buried and do not constitute selection guidance.

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