Skip to main content
Glama

企业微信应用号-发送图片消息

wework_app_send_image

Send image notifications to WeWork members using a URL. Optionally target specific users or send to all.

Instructions

通过企业微信应用号发送发送图片消息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes图片URL
touserNo接收消息的成员ID,多个用`|`分隔,为`@all`时向该企业应用全部成员发送,默认从环境变量获取

Implementation Reference

  • Tool handler for wework_app_send_image. Downloads the image from the provided URL and delegates to the wework_send_media helper with msgtype='image'.
    @mcp.tool(
        title="企业微信应用号-发送图片消息",
        description="通过企业微信应用号发送发送图片消息",
    )
    def wework_app_send_image(
        url: str = Field(description="图片URL"),
        touser: str = FIELD_TO_USER,
    ):
        return wework_send_media(touser, url, "image")
  • Helper function that downloads media from a URL, uploads it to WeWork's media/cgi-bin/media/upload API, then sends the media_id as a message to the WeWork app. Used by wework_app_send_image (and other media-sending tools).
    def wework_send_media(touser, url: str, msgtype=None):
        if msgtype:
            pass
        elif '.jpg' in url.lower() or '.jpeg' in url.lower() or '.png' in url.lower():
            msgtype = 'image'
        elif '.mp4' in url.lower():
            msgtype = 'video'
        elif '.arm' in url.lower():
            msgtype = 'voice'
        else:
            msgtype = 'file'
        res = requests.get(url, timeout=120)
        res.raise_for_status()
        file = io.BytesIO(res.content)
        mine = res.headers.get("content-type") or "application/octet-stream"
        res = requests.post(
            f"{WEWORK_BASE_URL}/cgi-bin/media/upload",
            params={"type": msgtype, "access_token": get_access_token()},
            files={"media": ("filename", file, mine)},
            timeout=120,
        )
        media = res.json() or {}
        if not (media_id := media.get("media_id")):
            return media
        res = requests.post(
            f"{WEWORK_BASE_URL}/cgi-bin/message/send?access_token={get_access_token()}",
            json={
                "touser": touser or WEWORK_APP_TOUSER,
                "agentid": WEWORK_APP_AGENTID,
                "msgtype": msgtype,
                msgtype: {"media_id": media_id},
            },
        )
        return res.json()
  • Input schema for wework_app_send_image: requires a 'url' (image URL) and optional 'touser' (recipient, defaults to env var WEWORK_APP_TOUSER).
    def wework_app_send_image(
        url: str = Field(description="图片URL"),
        touser: str = FIELD_TO_USER,
    ):
  • Registration of the wework module's tools (including wework_app_send_image) via wework.add_tools(mcp) called from __init__.py. The @mcp.tool decorator inside add_tools() registers it with FastMCP.
    wework.add_tools(mcp)
  • Helper that obtains and caches the WeWork API access token (1-hour TTL) used by wework_send_media and the app tools.
    @cached(TTLCache(maxsize=1, ttl=3600))
    def get_access_token():
        res = requests.get(
            f"{WEWORK_BASE_URL}/cgi-bin/gettoken",
            params={"corpid": WEWORK_APP_CORPID, "corpsecret": WEWORK_APP_SECRET},
            timeout=60,
        )
        return res.json().get("access_token")
Behavior2/5

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

With no annotations, the description carries the full burden. It only says '发送图片消息' but does not disclose any behavioral traits like image format requirements, size limits, or whether the operation is destructive. This is insufficient for an agent to understand the tool's behavior.

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

Conciseness3/5

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

The description is very short (one line) but contains a typo (duplicate '发送'). While concise, the typo reduces clarity. It is not front-loaded with key information.

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?

Given the tool has 2 parameters, no output schema, and no annotations, the description is minimal. It does not explain return values, error conditions, or the effect of the 'touser' parameter default behavior. Incomplete for practical use.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents both parameters. The description adds no additional meaning beyond the schema. Baseline 3 is appropriate as the description does not enhance parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states '通过企业微信应用号发送发送图片消息' which indicates sending image messages via WeChat Work application. However, the duplicate '发送' and lack of distinction from siblings like 'wework_send_image' or 'wework_app_send_file' make it vague. The purpose is clear but not specific enough to differentiate.

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 on when to use this tool versus alternatives such as 'wework_send_image' or other messaging tools. No context about when it is appropriate or when not to use it.

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/aahl/mcp-notify'

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