brewpage-mcp

Add token to profile

bind_token

Add an owner token to a BrewPage profile using that profile's admin token so the profile can publish content.

Instructions

Add an owner token to your BrewPage profile (as publish). Needs an admin token of that profile.

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": {
      "token": "<token>"
    },
    "name": "bind_token"
  }
}

Input Schema

Name	Required	Description	Default
`token`	Yes	Owner token to add
`ownerToken`	No	Admin token of the profile. Default: env BREWPAGE_OWNER_TOKEN (local server only).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.16.3Oct 30, 2026

changedInput schema / properties / ownerToken / description

Previous value: -"Admin token of the profile. Default: BREWPAGE_OWNER_TOKEN."New value: +"Admin token of the profile. Default: env BREWPAGE_OWNER_TOKEN (local server only)."

Changed2 schema fields changedv1.15.0Oct 27, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

Addedv1.13.0Oct 25, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive write, so the safety profile is covered. The description adds a genuinely useful behavioral fact beyond the annotations: the operation requires an admin token for that profile, which is an authorization requirement the agent must satisfy before calling.

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 compact sentences with the action front-loaded and the prerequisite second. The '(as publish)' fragment is the only piece that doesn't clearly earn its place, since it is unexplained.

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

Completeness3/5

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

For a small two-parameter mutation with no output schema, the description covers the action and the auth requirement but leaves gaps: it doesn't say what happens if the token is already bound, whether binding is reversible (no unbind sibling exists), or what a successful call returns or changes.

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 description coverage is 100%, so both 'token' and 'ownerToken' (including the env-var default) are fully documented in the schema. The description only restates that an admin token is needed, adding no format, scoping, or duplicate-handling semantics beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource: add an owner token to the BrewPage profile. The parenthetical '(as publish)' hints at the downstream use but is cryptic, and the description never distinguishes this from the sibling 'mint_token', which an agent could easily confuse it with.

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?

'Needs an admin token of that profile' gives a prerequisite, which is real guidance. However, there is no statement of when to bind versus when to mint a token, no exclusion of the other token-related siblings, and no note on whether a token can already be bound.

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