Skip to main content
Glama

List unanswered questions

list_unanswered_questions
Read-onlyIdempotent

Lists the questions the chat could not answer from one store's pages in the last 30 days, still open, the most recent first, with how many times each was asked. A page that answers one can be drafted for the person to publish. Needs the conversations permission and the store's switch for AI assistants in Settings > Security, and works only for stores the person owns.

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": {
      "store_id": "<store_id>"
    },
    "name": "list_unanswered_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
store_idYesThe store's store_id (not its name).

Output Schema

NameRequiredDescriptionDefault
daysNo
recordedNoFalse when handoff is off: no question is recorded then.
store_idYes
questionsYes
open_totalNo
dashboard_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), so the description's value is the extra operational context it supplies: the 30-day window, recency ordering, an aggregation of ask counts, and required prerequisites (conversations permission, the AI-assistants switch in Settings > Security, and store ownership). That is substantive beyond what the annotations declare, though it does not say what happens when prerequisites are unmet or whether results are paginated.

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?

Three sentences, front-loaded with what the tool returns before prerequisites and follow-up action. Wording is tight, with only mild redundancy between 'still open' and the 30-day window.

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 one-parameter read tool with a full output schema and covering annotations, the description supplies the essentials: scope, ordering, aggregation, permissions, and the follow-up action. Missing only edge behavior such as empty results or pagination limits.

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 coverage is 100% with a single store_id parameter, and the schema already warns that it is the store_id rather than the name. The description adds no parameter-level detail of its own, so the baseline 3 applies; an output schema exists, so return values need not be described here either.

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 with full scoping: 'the questions the chat could not answer from one store's pages in the last 30 days, still open, the most recent first, with how many times each was asked.' It is distinct from the conversation- and email-listing siblings, and the mention that a page can be drafted points at the related drafting tool.

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?

It gives clear context for use (unanswered, still-open questions in a 30-day window) and states the natural follow-up action of drafting a page that answers one. It stops short of naming an alternative or an explicit when-not-to-use condition, e.g. that per-conversation detail belongs to get_conversation.

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