Skip to main content
Glama

seodraft

by app.seodraft
OverviewDiscussionsAdmin

Get business profile

get_profile
Read-only

Read the workspace business profile. evidence is the bank, split in two: accepted is what an article may lean on and pending is what you proposed and the human has not ruled on yet; citing a pending piece in brief.evidence fails the rules as evidence-unaccepted. profileApprovedAt is null until the human approved the summary with approve_profile. siteInventory summarises the last import_sitemap run (status, pageCount, contentPages, contentPrefix, importedAt), or is null when the site was never imported. Every piece carries weakFirsthand: true means a classifier read it as a general market claim rather than something this business measured or lived. It is advisory, it never changed the status, and the flagged pieces sort to the top of the review queue. Flagged pending pieces are not accepted evidence; citing one in brief.evidence fails the rules as evidence-unaccepted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdNoThe workspace this call acts on, as listed by list_workspaces. Left out, the call uses the workspace the account is in right now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspaceId
      Added value: +{
+  "description": "The workspace this call acts on, as listed by list_workspaces. Left out, the call uses the workspace the account is in right now.",
+  "type": "string"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already establish it as a safe read (readOnlyHint=true, destructiveHint=false), and the description goes well beyond that: it explains the accepted/pending split, that profileApprovedAt is null until approve_profile runs, that siteInventory reflects the last import_sitemap, and that weakFirsthand is advisory-only and never alters status. That is rich domain behavior an agent cannot infer from annotations.

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

Conciseness3/5

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

Purpose is front-loaded and the info density is high, but the description is bloated and partly redundant: the rule that citing a pending piece in brief.evidence 'fails the rules as evidence-unaccepted' is stated twice, wasting space. It is more repetition than an agent needs.

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?

With no output schema, the return shape is entirely on the description, and it covers the profile's key structures (evidence bank, approval timestamp, site inventory, firsthand flag) thoroughly. For a read-only, single-optional-param tool this is complete enough to call correctly.

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% with a single optional workspaceId already fully documented in the schema (including the default behavior). The description adds no parameter-level detail, so the 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 clear verb+resource: 'Read the workspace business profile.' The read orientation implicitly distinguishes it from the update_profile sibling, but it never names that alternative or explicitly contrasts them, so it stops short of full sibling differentiation.

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?

Usage is only implied by explaining what the returned fields mean. It references approve_profile and import_sitemap as related concepts but does not state when to choose get_profile over alternatives or any preconditions for calling it.

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

All seodraft toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources