Skip to main content
Glama

Account, brands and settings

get_account
Read-only

Your Howseen account. Call view brands first when the account may track several brands. view: brands = the tracked brands (id, name, domain); usage = plan, quotas used and left, next scan, what this key may do; settings = brand profile, competitors, writing rules, Autopilot; connections = true state of every connection (CMS, feed, Search Console, GA4, Bing); billing = plan status, next payment, every quota of the period with its percentage, invoices. Read-only. Replies with metrics carry glossary: the dashboard's own explanation of each one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoWhat to return (default brands).
brandNoBrand id, name or domain (from get_account (view: brands)). Optional when the account has a single brand.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / view / enum
      Previous value: -[
      -  "brands",
      -  "usage",
      -  "settings",
      -  "connections"
      -]New value: +[
      +  "brands",
      +  "usage",
      +  "settings",
      +  "connections",
      +  "billing"
      +]
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive and closed-world, so the safety bar is low; the description still adds that metric-bearing replies include a glossary explaining each metric, which is real context about response content. It does not cover pagination, auth requirements, or failure behavior.

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?

Front-loaded with the resource identity and the one ordering rule, then a compact per-view breakdown. The single long semicolon-delimited sentence is dense but every clause maps to a distinct view; no filler.

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?

With no output schema, the description carries the burden of describing returns and does so view by view, including non-obvious content like connection truth state and per-quota percentages. Only minor gaps remain around defaults and error conditions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes further by explaining what each enum value actually returns (usage = plan, quotas, next scan, key permissions; billing = plan status, payment, quota percentages, invoices). That adds meaning the enum list alone does not carry.

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 resource ('Your Howseen account') and enumerates the five views it can return, each with the payload it contains. An agent can tell this apart from mutation siblings like update_settings because the description declares 'Read-only'.

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?

Gives explicit sequencing guidance: call view brands first when the account may track several brands, since brand identifiers come from there. It stops short of naming other tools or stating when a different tool would be better, so it is clear context without full alternatives coverage.

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.