Skip to main content
Glama
Sign In

GenFlick

by com.genflick
OverviewDiscussionsAdmin

social read workspace

native.social_read_workspace
DestructiveIdempotent

Read accounts, drafts, assets, policy, events and destination previews. draftId loads the full saved document.

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": {
      "work_id": "<work_id>",
      "arguments": "<arguments>",
      "expected_catalog_version": "<expected_catalog_version>",
      "read_skills": "<read_skills>",
      "request_key": "<request_key>"
    },
    "name": "native.social_read_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
work_idYes
argumentsYes
read_skillsYesExact required native skills and their dependencies, copied from the accepted session bootstrap's skills array. Include only entries in that array. General mcp.* guides and native.{studio}.instructions are guidance, not native skill proofs.
request_keyYes
publication_proposal_idNoFor native Social scheduling, the exact server-approved publication proposal. This identifier cannot confer approval by itself.
expected_catalog_versionYesFor a new session, read a studios/{studio}/native/{pack} child toolset and copy invocation.catalog_version from a native tool descriptor. Do not use the top-level library version. For calls in an existing session, use that session proposal's catalog_version.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior1/5

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

The description frames this as a pure read ('Read accounts, drafts, assets...'), while the annotations declare readOnlyHint=false and destructiveHint=true. An agent trusting the description would assume a safe inspection call and could be surprised by a tool flagged as mutating and destructive; that divergence is never reconciled or explained in the text. Beyond this conflict, no behavioral context is added (no permission, session, or side-effect disclosure) despite the session-bound parameters.

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 short sentences with zero filler, and the resource enumeration is front-loaded before the draftId mode note. It is efficient rather than padded; the brevity is only a problem because content is missing, not because wording is wasted.

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

Completeness2/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 described. But this is a complex, session-scoped tool with five required parameters including opaque plumbing (request_key, read_skills, expected_catalog_version) and a nested arguments object, none of which the description addresses. Given that complexity and the annotation tension, the definition is too thin to call confidently.

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

Parameters2/5

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

Schema description coverage is only 50% across six parameters with a nested arguments object, so the description needs to carry real weight. It clarifies exactly one: draftId loads the full saved document, which genuinely extends the schema's vague 'Observed workspace ID'. The other five (work_id, request_key, arguments.from/until/mediaCursor/mediaSearch, read_skills, expected_catalog_version) get no explanation in the description.

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?

The description names a specific verb (read) plus a concrete resource set: accounts, drafts, assets, policy, events, destination previews. An agent can tell this is the aggregate workspace-snapshot reader rather than a narrow getter. It stops short of differentiating from sibling readers such as native.social_read_queue, native.list_social_destinations, or get_social_publication, whose scopes overlap.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: no condition selecting this over native.social_read_queue or list_social_destinations, and no note on whether it is the first call in a social workflow. The only usage-shaped hint is that supplying draftId switches to loading a full saved document, which is a mode toggle rather than routing guidance.

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

All GenFlick 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