Skip to main content
Glama

set_cover_image

Assign a cover thumbnail to a draft using a CDN URL from upload_image or any public URL, and receive an updated draft summary.

Instructions

Set the cover (thumbnail) image for a draft.

The cover image is shown on the publication homepage, in social shares, and as the email header. Use upload_image first to get a CDN URL.

Args: post_id: Draft ID. image_url: Substack CDN URL from upload_image, or any public image URL.

Returns: Updated draft summary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
post_idYes
image_urlYes

Implementation Reference

  • MCP tool handler for set_cover_image: validates args via type hints, delegates to SubstackClient.set_cover_image.
    @mcp.tool()
    def set_cover_image(post_id: str, image_url: str) -> dict:
        """Set the cover (thumbnail) image for a draft.
    
        The cover image is shown on the publication homepage, in social shares,
        and as the email header. Use upload_image first to get a CDN URL.
    
        Args:
            post_id: Draft ID.
            image_url: Substack CDN URL from upload_image, or any public image URL.
    
        Returns:
            Updated draft summary.
        """
        return _get_client().set_cover_image(post_id=post_id, image_url=image_url)
  • Tool registration via @mcp.tool() decorator on set_cover_image function.
    @mcp.tool()
  • SubstackClient.set_cover_image implementation: calls self._api.put_draft with cover_image=image_url, returns draft summary.
    def set_cover_image(self, post_id: str, image_url: str) -> dict:
        result = self._api.put_draft(post_id, cover_image=image_url)
        return self._summarize_draft(result)
Behavior4/5

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

With no annotations, the description carries the burden of behavioral disclosure. It explains where the cover image is used (homepage, social shares, email header) and notes the return type (updated draft summary). It does not mention side effects like overwriting, but the behavior is largely implied.

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?

Four sentences, front-loaded with purpose, followed by context, argument details, and return. No redundant information. Every sentence adds value.

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?

Given the simplicity (2 params, no output schema), the description covers essential usage: purpose, prerequisite (upload_image), parameter semantics, and return value. It lacks info on idempotency or error handling, but completeness is adequate for this tool.

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?

Input schema has 0% coverage, but the description adds meaning beyond property names. It specifies 'post_id: Draft ID' and 'image_url: Substack CDN URL from upload_image, or any public image URL.' This clarifies valid values and origin requirements.

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?

The description clearly states the tool's action: 'Set the cover (thumbnail) image for a draft.' The verb 'set' and resource 'cover image' are specific and distinct from sibling tools like upload_image or update_draft.

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

Usage Guidelines4/5

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

The description provides explicit guidance: 'Use upload_image first to get a CDN URL.' It also clarifies that image_url can be 'any public image URL', not just from upload_image. This helps the agent understand prerequisites and alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nanameru/substack-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server