Skip to main content
Glama
storelift-mcp

storelift-mcp

List tracked apps

list_apps
Read-onlyIdempotent

Lists the apps tracked in your Storelift account with their IDs, names, countries and keywords. Call it first to get the appId every other tool requires.

Instructions

List the apps tracked in this Storelift account (id, name, countries, keywords). Call this first — every other tool needs an appId from here.

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_apps"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile needs no elaboration here. The description adds account scoping ('this Storelift account') and the key returned fields, but says nothing about result size, ordering, or whether the list is paginated or cached.

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?

Two sentences, zero filler: the resource and returned fields come first, and the usage directive follows and is emphasized with a dash. Nothing could be removed without losing information.

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?

With no input parameters and no output schema, the description carries the return-value burden and discharges it by naming the fields returned. It also supplies the one piece of workflow context an agent needs: that the returned appId gates every other tool.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning to convey. The description does not need to compensate for anything on this axis.

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 names a specific verb and resource plus its scope: 'apps tracked in this Storelift account', and it lists the returned fields (id, name, countries, keywords). The account-tracking scope partially separates it from search-oriented siblings like find_apps and hive_search_apps, but it never names those alternatives, so an agent must still infer the boundary.

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?

'Call this first — every other tool needs an appId from here' gives explicit ordering and prerequisite guidance that most tool descriptions omit. It does not state any when-not condition or name the search alternative (find_apps) that an agent might otherwise reach for, so it stops short of full routing guidance.

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