Skip to main content
Glama

legal_get_consent

Retrieves cookie consent banner configuration for a WordPress site, including enabled status, GTM/GA4/ads settings, privacy and imprint pages, and logging options.

Instructions

Get the cookie consent banner configuration: enabled, gtm_id, loader_url, ga4_id, ahrefs_key, ads_id, gtm_services { analytics, marketing }, privacy_page, imprint_page, log_enabled, backdrop. Change it with legal_put_consent.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>"
    },
    "name": "legal_get_consent"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.4.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden, and 'Get' plus the explicit pointer that changes happen via legal_put_consent makes clear this tool is side-effect free. The field list also discloses the shape of what comes back, including potentially sensitive keys (ahrefs_key, ads_id), though permissions or defaults are not mentioned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both front-loaded with the essential information: what is returned, then how to change it. The long comma-separated field list is dense but earns its place because there is no output schema.

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 one-parameter read tool with no annotations and no output schema, the description supplies the return-field inventory and the mutation alternative, which is most of what an agent needs. Minor gaps remain around access requirements and default values when consent is unconfigured.

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?

The single parameter 'site' is already fully documented in the schema, including the 'see list_sites' pointer, so the description adds no meaning beyond it. Baseline 3 applies given 100% schema description coverage.

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?

States a specific verb (Get) and a precisely scoped resource (the cookie consent banner configuration), then enumerates the exact fields returned, so an agent knows what it gets without opening a schema. It also names the mutating counterpart legal_put_consent, which separates it cleanly from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The closing sentence 'Change it with legal_put_consent' gives explicit routing to the write alternative, so the read/write split is unambiguous. It does not spell out when-not conditions (e.g. reading consent logs instead), but for a simple getter the primary alternative is covered.

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