Mark

Get Workspace

get_workspace

Read-onlyIdempotent

Shows which Mark workspace you're acting in: your role, timezone, members, sites, integrations, a short line per channel (connected account, approval mode), and what needs attention now (posts awaiting review, search exceptions, readiness issues). mcpUrl is this workspace's own MCP address, for adding it as a separate connector in clients like Claude that take each URL once. Use it first in a session, or when switching tasks, to see the workspace state. For which social accounts are connected and each channel's rules, call list_channels. For website posts (blog, FAQ, competitor pages), call get_website_cms. Does not change anything. Related: list_channels, get_brand_context, list_connections, search_posts, get_website_cms.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`role`	Yes
`orgId`	Yes
`sites`	Yes
`appUrl`	Yes
`mcpUrl`	Yes
`members`	Yes
`channels`	Yes
`timezone`	Yes
`connections`	Yes
`needsAttention`	Yes
`businessAliases`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 20, 2026

addedOutput schema / properties / businessAliases

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "appUrl",
-  "channels",
-  "connections",
-  "mcpUrl",
-  "members",
-  "name",
-  "needsAttention",
-  "orgId",
-  "role",
-  "sites",
-  "timezone"
-]New value: +[
+  "appUrl",
+  "businessAliases",
+  "channels",
+  "connections",
+  "mcpUrl",
+  "members",
+  "name",
+  "needsAttention",
+  "orgId",
+  "role",
+  "sites",
+  "timezone"
+]

Changed2 schema fields changedOct 14, 2026

addedOutput schema / properties / mcpUrl
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "appUrl",
-  "channels",
-  "connections",
-  "members",
-  "name",
-  "needsAttention",
-  "orgId",
-  "role",
-  "sites",
-  "timezone"
-]New value: +[
+  "appUrl",
+  "channels",
+  "connections",
+  "mcpUrl",
+  "members",
+  "name",
+  "needsAttention",
+  "orgId",
+  "role",
+  "sites",
+  "timezone"
+]

First observedOct 1, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered; the description reinforces it with 'Does not change anything.' It adds real value beyond annotations by disclosing the return payload and the mcpUrl connector nuance, though it says nothing about response size or cost.

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: the resource and its payload lead, then usage, then alternatives. The first sentence is long and parenthetical, but every clause earns its place and nothing is redundant filler.

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?

An output schema exists, so return values need not be explained, yet the description goes further and helps the agent interpret them. Combined with usage guidance, sibling routing and a no-side-effects statement, nothing an agent needs to call this correctly is missing.

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?

Zero input parameters, so the schema has nothing to describe and there is no risk of misuse. The description adds meaning by framing the parameterless call as a session-context snapshot. Baseline 4 applies for a no-parameter tool.

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 (the Mark workspace) and enumerates the concrete contents an agent gets back (role, timezone, members, sites, integrations, channel status, attention items, mcpUrl). It also names the siblings it is not (list_channels, get_website_cms) and the conditions that select each.

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

Usage Guidelines5/5

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

Explicitly says when to use it ('first in a session, or when switching tasks') and routes alternative needs to specific siblings: list_channels for connected accounts/channel rules, get_website_cms for blog/FAQ/competitor pages. When-not guidance is implicit but the routing is unambiguous.

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

All Mark tools Inspect

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

Need Help?