@applyra/mcp-server

List notes

list_notes

Read-only

Retrieve an app's chart notes—daily actions like giveaways or keyword changes—to compare them against visibility and rank data. Returns dated notes with scope, oldest first.

Instructions

List the notes on an application's charts: what the user did on a day ("launched a Reddit giveaway", "changed keywords"), to read the visibility and ranks against it. Returns app_id and notes[] of { id, number, day (YYYY-MM-DD), text, scope }, oldest first. number is the note's rank among all the app's notes, the number the charts print on its flag; scope is "app" for a note shown on every market of the app, "market" for one shown on this market only. Pass the numeric internal ID from list_applications. To see what followed each note, use compare_events. Read-only.

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": {
      "app_id": "<app_id>"
    },
    "name": "list_notes"
  }
}

Input Schema

Name	Required	Description	Default
`app_id`	Yes	The application internal ID (numeric, from list_applications results)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.7.0Oct 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, so the safety profile is covered. The description goes beyond them by disclosing the return shape (app_id and notes[]), ordering ('oldest first'), and semantics of the tricky fields (number, scope), which is valuable given no output schema exists.

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?

Front-loaded with purpose, then return format, then routing. The field-by-field explanation of number and scope is slightly verbose but each sentence carries information an agent needs; overall it is efficient rather than padded.

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

Completeness5/5

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

For a read-only single-parameter tool with no output schema, the description supplies the return structure, ordering, field meaning, ID provenance, and the natural next step (compare_events). Nothing needed to invoke or interpret it is missing.

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?

With 100% schema coverage on a single parameter, the schema already documents app_id fully. The description's 'Pass the numeric internal ID from list_applications' reinforces source/format but adds little beyond the schema's own 'numeric, from list_applications results' wording, so 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 ('List the notes on an application's charts') and immediately grounds it with concrete examples ('launched a Reddit giveaway', 'changed keywords'). It distinguishes itself from the write siblings by noting it is read-only and routes to compare_events as the follow-on 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?

Gives clear usage context ('Pass the numeric internal ID from list_applications') and names an alternative ('To see what followed each note, use compare_events'). It does not state when *not* to use this tool, so it falls short of a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.