Skip to main content
Glama

AceRound AI Interview Copilot

list_my_feedbacks

Read-only

List the user's feedback, one per line, most recently updated first, 20 per page: status, number of replies, unread replies, and the latest message. (Requires the user's sign-in with scope account:read.)

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

Input Schema

NameRequiredDescriptionDefault
pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: sort order (most recently updated first), page size (20 per page), the shape of each row, and the required account:read scope for sign-in.

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?

One front-loaded sentence stating the action, ordering, page size and row fields, followed by a short parenthetical on auth scope. No filler and no repetition of the name or title.

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 simple read-only list tool with no output schema, the description covers ordering, page size, returned fields and auth requirements. The remaining gap is pagination termination (total count or empty-page signal), which an agent needs to iterate correctly.

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 0%, so the description must carry the load for the single page parameter. It gives the page size (20 per page), which lets an agent infer offset semantics, but says nothing about the 1-100 range, the default of 1, or how to detect the last page. Partially compensatory.

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 description opens with a specific verb and resource ("List the user's feedback") and goes on to enumerate the per-item fields returned (status, reply counts, unread replies, latest message). It does not explicitly differentiate itself from the sibling get_my_feedback, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is implied by the wording: this is the bulk listing of the signed-in user's feedback, most recent first. There is no explicit statement of when to prefer this over get_my_feedback (for a single item's detail) or list_my_hot_words, and no exclusions are given.

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