list_guidelines
List the organization’s guideline documents — brand voice, platform playbooks, and org-specific rules. Returns metadata only; use get_guideline to fetch the full markdown.
Parameters#
None.
Returns#
json
{
"guidelines": [
{
"slug": "brand",
"path": "guidelines/brand.md",
"content_type": "markdown",
"version": 3,
"pinned_in_prompt": true,
"frontmatter": { "requires": [] },
"updated_at": "2026-04-15T12:00:00Z"
},
{
"slug": "meta",
"path": "guidelines/meta.md",
"content_type": "markdown",
"version": 1,
"pinned_in_prompt": false,
"frontmatter": { "requires": ["meta_ads"] },
"updated_at": "2026-04-10T09:30:00Z"
}
],
"count": 2,
"source": "adlyse.guidelines@v1"
}| Field | Description |
|---|---|
guidelines[].slug | Short identifier (e.g. brand, adlyse, google, meta, or custom) |
guidelines[].pinned_in_prompt | true if this guideline is injected into the in-app assistant every turn |
guidelines[].frontmatter | Parsed YAML; requires lists platform gating (meta_ads, google_ads) |
guidelines[].version | Incremented on every edit |
Errors#
error_type | When |
|---|---|
auth_error | Missing / invalid API key |
System slugs#
| Slug | Purpose |
|---|---|
adlyse | Overarching assistant instructions — tone, caution, escalation |
brand | Brand voice, audience, product, taboos |
google | Google Ads-specific playbook (only injected when a Google account is connected) |
meta | Meta Ads-specific playbook (only injected when a Meta account is connected) |
Orgs can also create custom slugs; they appear in this list alongside the system ones.
Example#
Response: as shown above.
See also#
get_guideline— full markdown content- Guidelines — authoring UI and draft review flow