Skip to main content
Glama
Sign In
Kleap

Kleap

Official
by kleaphq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

list_apps

Retrieve a paginated list of websites owned by your account on Kleap. Use offset and limit to control results.

Instructions

List the Kleap apps (websites) owned by the authenticated account.

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
limitNoMax apps to return (default 20).
offsetNoPagination offset (default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries burden. It correctly implies a non-destructive read operation but does not disclose potential limits, rate limits, or empty result behavior. The statement is minimal but accurate.

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?

Single, front-loaded sentence with no extraneous words. Every word contributes to clarity. Highly efficient.

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 list tool with fully described parameters, the description is complete. It specifies ownership filter and result type. Could mention pagination or return format, but not critical given schema.

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 100%, so baseline is 3. The description adds no extra detail about parameters beyond what the schema already provides (limit, offset descriptions). No parameter intuition added.

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?

The description clearly states the action ('List'), the resource ('the Kleap apps/websites'), and the scope ('owned by the authenticated account'). It effectively distinguishes from siblings like 'get_app' (single app) and 'create_app' (creation).

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?

The description implies use for listing owned apps but provides no explicit guidance on when not to use or alternatives. It does not mention pagination parameters or context for limit/offset usage.

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

Deploy Server

Other Tools