Skip to main content
Glama
ZatesloFL

Google Workspace MCP Server

by ZatesloFL

create_presentation_comment

Add comments to Google Presentations by specifying user email, presentation ID, and comment content for collaborative feedback and review.

Instructions

Create a new comment on a Google Presentation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
comment_contentYes
presentation_idYes
user_google_emailYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Dynamically generated handler function for the 'create_presentation_comment' tool. Decorated and named within the factory, it invokes the core comment creation implementation.
    @require_google_service("drive", "drive_file")
    @handle_http_errors(create_func_name, service_type="drive")
    async def create_comment(service, user_google_email: str, presentation_id: str, comment_content: str) -> str:
        """Create a new comment on a Google Presentation."""
        return await _create_comment_impl(service, app_name, presentation_id, comment_content)
  • Core implementation logic that uses the Google Drive API to create a new comment on the specified file (presentation). Handles the API call and formats the response.
    async def _create_comment_impl(service, app_name: str, file_id: str, comment_content: str) -> str:
        """Implementation for creating a comment on any Google Workspace file."""
        logger.info(f"[create_{app_name}_comment] Creating comment in {app_name} {file_id}")
    
        body = {"content": comment_content}
    
        comment = await asyncio.to_thread(
            service.comments().create(
                fileId=file_id,
                body=body,
                fields="id,content,author,createdTime,modifiedTime"
            ).execute
        )
    
        comment_id = comment.get('id', '')
        author = comment.get('author', {}).get('displayName', 'Unknown')
        created = comment.get('createdTime', '')
    
        return f"Comment created successfully!\\nComment ID: {comment_id}\\nAuthor: {author}\\nCreated: {created}\\nContent: {comment_content}"
  • Sets the __name__ of the generated functions to 'create_presentation_comment' etc., and registers them as MCP tools using server.tool().
    read_comments.__name__ = read_func_name
    create_comment.__name__ = create_func_name
    reply_to_comment.__name__ = reply_func_name
    resolve_comment.__name__ = resolve_func_name
    
    # Register tools with the server using the proper names
    server.tool()(read_comments)
    server.tool()(create_comment)
    server.tool()(reply_to_comment)
    server.tool()(resolve_comment)
  • Invokes the comment tools factory specifically for presentations/slides, assigns the functions including 'create_presentation_comment', and provides slide-specific aliases.
    # Create comment management tools for slides
    _comment_tools = create_comment_tools("presentation", "presentation_id")
    read_presentation_comments = _comment_tools['read_comments']
    create_presentation_comment = _comment_tools['create_comment']
    reply_to_presentation_comment = _comment_tools['reply_to_comment']
    resolve_presentation_comment = _comment_tools['resolve_comment']
    
    # Aliases for backwards compatibility and intuitive naming
    read_slide_comments = read_presentation_comments
    create_slide_comment = create_presentation_comment
    reply_to_slide_comment = reply_to_presentation_comment
    resolve_slide_comment = resolve_presentation_comment
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Create' implies a write/mutation operation, the description doesn't address permissions needed, whether comments are public/private, rate limits, or what the output contains. It provides minimal behavioral context beyond the basic action.

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, efficient sentence that states the core functionality without unnecessary words. It's appropriately sized for a basic tool description and front-loads the essential information.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that there's an output schema (which handles return values) and no annotations, the description provides minimal but adequate context for a simple creation tool. However, with 3 undocumented parameters and no behavioral guidance, it leaves significant gaps that the agent must infer from the tool name and schema structure alone.

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 all 3 parameters are undocumented in the schema. The description adds no information about parameter meanings, formats, or constraints. It doesn't explain what 'presentation_id' should look like, what 'comment_content' can contain, or why 'user_google_email' is required for comment creation.

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 ('Create a new comment') and target resource ('on a Google Presentation'), providing specific verb+resource pairing. However, it doesn't distinguish this tool from sibling comment tools like 'create_document_comment' or 'create_spreadsheet_comment', which follow the same pattern for different Google Workspace apps.

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 about when to use this tool versus alternatives. The description doesn't mention sibling tools like 'reply_to_presentation_comment' or 'resolve_presentation_comment', nor does it specify prerequisites (e.g., needing edit access to the presentation) or appropriate contexts for comment creation.

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/ZatesloFL/google_workspace_mcp'

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