Read a resource
Loading server catalog…. Download catalog
https://app.advarde.com/mcpAvailable subject to your connection’s permissions.
Description: Read a built-in workflow guide by its exact resource URI.
Method: resources/read
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.
uristringrequired["buro://optimization/guide","buro://campaigns/guide","buro://automation/guide","buro://conversions/guide","buro://ads/guide","buro://marketing/guide"]Full JSON Schema
{
"type": "object",
"properties": {
"uri": {
"type": "string",
"enum": [
"buro://optimization/guide",
"buro://campaigns/guide",
"buro://automation/guide",
"buro://conversions/guide",
"buro://ads/guide",
"buro://marketing/guide"
]
}
},
"required": [
"uri"
]
}Available resources
buro://optimization/guideCreative optimization and approval inbox
Recurring agent reviews, frozen proposals, user approval and durable publishing.
buro://campaigns/guideCampaign creation and launch
Shared saved drafts, paused builds, recovery and reviewed scheduled activation.
buro://automation/guideAccount management and automation
Versioned policies, evidence, limits, supporting data and stops.
buro://conversions/guideConversion presets and installation
Shared browser/MCP setups, safe provisioning, installation and event verification.
buro://ads/guideAds management guide
Workspace boundaries, bidding units, pagination, and mutation workflow.
buro://marketing/guideMarketing 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.