Skip to content
advardeDeveloper docs
v1.0

List resources

Loading server catalog…. Download catalog

POSThttps://app.advarde.com/mcp
Protocol

Available subject to your connection’s permissions.

Description: List built-in workflow guides and their resource URIs.

Method: resources/list

Output: See the protocol description and workflow notes below.

Access: Workspace-scoped MCP authentication.

Authentication

Use an MCP access token from MCP connections, or connect through OAuth. Send your token in the Authorization: Bearer header.

For full protocol initialization and tool discovery, use an MCP client. These examples show individual JSON-RPC requests.

Request parameters

Send these fields inside params. The JSON-RPC envelope is shown in the request example.

cursorstringoptional

Opaque nextCursor from a previous resources/list response.

Full JSON Schema
{
  "type": "object",
  "properties": {
    "cursor": {
      "type": "string",
      "description": "Opaque nextCursor from a previous resources/list response."
    }
  },
  "additionalProperties": false
}

Available resources

buro://optimization/guide

Creative optimization and approval inbox

Recurring agent reviews, frozen proposals, user approval and durable publishing.

buro://campaigns/guide

Campaign creation and launch

Shared saved drafts, paused builds, recovery and reviewed scheduled activation.

buro://automation/guide

Account management and automation

Versioned policies, evidence, limits, supporting data and stops.

buro://conversions/guide

Conversion presets and installation

Shared browser/MCP setups, safe provisioning, installation and event verification.

buro://ads/guide

Ads management guide

Workspace boundaries, bidding units, pagination, and mutation workflow.

buro://marketing/guide

Marketing workflows

Reusable knowledge, inspiration, images, reports and alerts. Performance imports are disabled by default.

Responses

200Successful protocol response

Inspect result.isError for tool-level failures, even when the HTTP status is 200.

202Notification accepted

MCP notifications return no JSON-RPC response body.

400Invalid request

Check the JSON-RPC envelope, parameters, and protocol version.

406Not acceptable

Accept must include application/json and text/event-stream.

429Rate limited

Wait for the Retry-After interval before making another request.

401Unauthorized

A valid, unexpired MCP bearer token is required.

403Access denied

Your connection needs access to this workspace and the requested operation.

Advarde MCP API v1.0