Skip to main content
GET
List an app's tools
Without q, every tool of the app, most used first. Some apps have hundreds; page with limit and cursor. With q, a task in plain words such as unread emails from my boss, you get only the few tools that do it, best first, with plan (steps that usually do the task) and pitfalls. This answer is one page. Each tool has its inputs (name, type, description, required) and its kind: read or write. See Read and write. Run one with Run an app tool. Needs apps:read. MCP tool: list_app_tools.

Authorizations

Authorization
string
header
required

API key with the vd_sk_ prefix, as Authorization: Bearer vd_sk_.... Create keys in Settings → API Keys.

Path Parameters

app
string
required

Query Parameters

q
string | null

A task in plain words: only the tools that do it, best first, with a plan (no paging).

Maximum string length: 300
limit
integer
default:100

Items per page, 1–100.

Required range: 1 <= x <= 100
cursor
string | null

next_cursor of the previous page.

Response

The app's tools.

tools
AppTool · object[]
required
has_more
boolean
required
read-only

True when there is a next page (next_cursor is not null).

next_cursor
string | null

Pass as ?cursor= for the next page; null on the last page.

plan
string[]

With q: steps that usually do the task.

pitfalls
string[]

With q: mistakes to avoid.