Skip to main content
Glama

Save author profile

save_author_profile
Destructive

Creates or replaces an author profile of a site, the same as in Keytomic. Articles can name an author and use their bio, credentials and writing voice. Without authorProfileId it creates an author from every author field; calling it twice creates two authors. A site has at most 3 authors, and the first author becomes the default and turns authors on. With authorProfileId and the author fields it replaces that author, so send every field; the settings section of get_project returns the current values. makeDefault makes the saved author the site’s default author and turns authors on; articles without their own author use the default. With only authorProfileId and makeDefault it only sets the default. Spends no credits.

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": {
      "projectId": "<projectId>"
    },
    "name": "save_author_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
bioNo
fullNameNo
photoUrlNo
projectIdYesSite to act on, from list_sites.
roleTitleNo
socialUrlNo
credentialsNo
makeDefaultNoMakes the saved author the site’s default author and turns authors on.
writingVoiceNo
authorProfileIdNoAuthor profile to replace or make the default, from the settings section of get_project. Leave it out to create an author.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

Beyond annotations (destructive, non-idempotent), the description discloses full-replacement semantics, the 3-author limit, automatic default-author assignment, and that the call spends no credits. These details add concrete operational context not visible in the annotations.

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?

The description is front-loaded with the core operation and then systematically covers modes, limits, and side effects. It is dense and occasionally repetitive ('turns authors on' appears twice), but every sentence conveys actionable information.

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?

For a 10-parameter destructive mutation with low schema coverage and no output schema, the definition covers the critical decision points: create vs replace, default handling, author limits, and credit cost. It omits edge-case error behavior (e.g., exceeding 3 authors), but the core operational picture is complete.

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?

With only 30% schema coverage, the description compensates significantly: it explains that all author fields are consumed on creation, that replacement requires sending every field, and that makeDefault and authorProfileId have special modes. It does not describe every field individually (e.g., roleTitle, socialUrl), but the key parameter interactions are made explicit.

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 states a specific upsert operation for an author profile of a site and explicitly covers both create and replace modes. It does not name sibling delete_author_profile, but its create/replace scope clearly separates it from deletion and read-only siblings like get_project.

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?

It explains precisely when to omit authorProfileId (creation) versus when to supply it with all fields (replacement), warns that calling twice creates duplicate authors, and describes the makeDefault-only mode. It also notes the 3-author cap and default-author behavior, leaving little ambiguity about invocation modes.

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.

Resources