Skip to main content
Glama
Sign In
Publer Gateway MCP

Publer Gateway MCP

by dougm1966
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

publer_set_project_default

Set a project's default workspace and optional account IDs to enable streamlined social scheduling and approval workflows.

Instructions

Set a local non-secret project default workspace and optional account IDs.

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": {
      "workspaceId": "<workspaceId>"
    },
    "name": "publer_set_project_default"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdsNo
projectPathNo
workspaceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only indicates the operation is a set (mutation) and 'non-secret', but does not explain side effects, error conditions, permission requirements, or reversibility.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with no unnecessary words. Every word carries meaning, making it efficiently concise.

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?

For a simple setter tool with three parameters and no output schema, the description is incomplete. It fails to explain what 'default' means, the role of projectPath, or the overall effect of calling this tool. The agent lacks sufficient context to use it correctly.

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 0%, so the description must compensate. It mentions workspaceId and accountIds but does not describe projectPath, leaving one parameter undocumented. No details on format, constraints, or allowed values are provided.

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 clearly states the action (set) and the target (local non-secret project default workspace and optional account IDs). It distinguishes from the sibling tool 'publer_get_project_default' which retrieves defaults. However, the term 'local' is ambiguous and could be clearer.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, such as the existence of a project, or when setting defaults is appropriate.

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

Deploy Server

Other Tools