Skip to main content
Glama

BRAINIAC Web Technology Fingerprinting

Decode IAB TCF v2 TC string

web-technology_tcf-consent-string-decode
Read-onlyIdempotent

Decode an IAB Europe TCF v2.x transparency and consent string into purposes, vendors and publisher restrictions. Price $0.03 USDC. POST /api/v1/web-technology/tcf-consent-string-decode. An unpaid call returns the x402 payment terms and does not run.

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": {
      "tcString": "<tcString>"
    },
    "name": "web-technology_tcf-consent-string-decode"
  }
}

Input Schema

NameRequiredDescriptionDefault
tcStringYestcString, string, length 1 to 10000. Required.

Output Schema

NameRequiredDescriptionDefault
cmpIdNocmpId. Number.
createdNocreated. String.
sourcesNosources. Array.
versionNoversion. Number.
segmentsNosegments. Array.
cmpVersionNocmpVersion. Number.
lastUpdatedNolastUpdated. String.
limitationsNolimitations. Array.
publisherCCNopublisherCC. String.
consentScreenNoconsentScreen. Number.
vendorConsentsNovendorConsents. Array.
consentLanguageNoconsentLanguage. String.
purposeConsentsNopurposeConsents. Array.
tcfPolicyVersionNotcfPolicyVersion. Number.
isServiceSpecificNoisServiceSpecific. Boolean.
vendorListVersionNovendorListVersion. Number.
purposeOneTreatmentNopurposeOneTreatment. Boolean.
specialFeatureOptinsNospecialFeatureOptins. Array.
useNonStandardStacksNouseNonStandardStacks. Boolean.
publisherRestrictionsNopublisherRestrictions. Array.
vendorLegitimateInterestsNovendorLegitimateInterests. Array.
purposeLegitimateInterestsNopurposeLegitimateInterests. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the price, the HTTP endpoint, and, importantly, that an unpaid call returns x402 payment terms instead of running. This adds concrete operational context about cost and payment gating that the annotations do not provide.

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

Conciseness5/5

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

The description is short, front-loaded with the core decode operation, and then adds only the cost, endpoint, and unpaid-call behavior. Every sentence carries relevant information and there is no redundant text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter decode tool with an output schema and read-only annotations, the description supplies the important missing context: what the input represents, what the output contains, and how payment affects execution. No essential calling information appears to be omitted.

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?

Schema coverage is 100%, so the input schema already documents the required tcString field and its length constraints. The description adds that the string is an IAB Europe TCF v2.x consent string, but it does not provide additional format or encoding details beyond that semantic label.

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?

The description gives a specific verb, 'Decode', and a precise resource, an IAB Europe TCF v2.x transparency and consent string, plus the decoded outputs: purposes, vendors, and publisher restrictions. That is substantially more specific than the title alone and clearly separates it from the neighboring web-technology detection, validation, and parsing tools.

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

Usage Guidelines3/5

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

The description makes clear that the tool is for decoding TCF v2.x consent strings and that unpaid calls do not execute, which implies the main usage context and prerequisite. However, it does not explicitly state when to use this versus alternatives or when not to use it, leaving that guidance inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources