> ## Documentation Index > Fetch the complete documentation index at: https://docs.zuddl.com/llms.txt > Use this file to discover all available pages before exploring further. # Update Sponsor > **Tool name:** `v1_update_sponsor` ยท **Behaviour:** โœ๏ธ Write ยท ๐Ÿ” Idempotent Change the details of a sponsor on an event in your Zuddl organization. Send only the fields you want to change; anything you omit keeps its current value. Social links you supply are merged by type โ€” a link you name is replaced, a link sent as an empty string is removed, and one you omit is left alone โ€” while the sponsor's tier, booth, assigned tasks and uploaded files keep their current values. On events with the exhibitor portal the attached booth's name and description are derived from the sponsor, so changing the name or tagline re-derives them. Images are not settable here โ€” use v1_upload_sponsor_image. Returns the updated sponsor. **Same as Public API:** [Update a sponsor](/api-reference/sponsors/update-a-sponsor) (`PATCH /v1/events/{eventId}/sponsors/{sponsorId}`) ## OpenAPI ````yaml https://api.prod.zuddl.com/api/v3/api-docs/mcp-tools post /tools/v1_update_sponsor openapi: 3.1.0 info: title: Zuddl MCP Tools Reference description: >- The Zuddl MCP server lets AI assistants such as Claude and ChatGPT work with your Zuddl organization through the [Model Context Protocol](https://modelcontextprotocol.io). This reference lists every tool the server offers. It is generated from the live server, so it always matches what your assistant sees. # Connecting Add `https://setup.zuddl.com/api/mcp` as a remote MCP server in your assistant. It signs you in to Zuddl with OAuth and then calls tools on your behalf, with your permissions. AI features must be enabled for your organization. # Calling a tool Assistants call a tool with a JSON-RPC `tools/call` request whose `name` is the tool name and whose `arguments` match the request body documented on the tool's page. The `/tools/` paths in this reference identify tools; they are not HTTP endpoints. # Behaviour labels | Label | Meaning | | --- | --- | | ๐Ÿ”’ Read-only | Reads data and changes nothing. | | โœ๏ธ Write | Creates or updates data, but does not delete it. | | โš ๏ธ Destructive | Deletes or removes data. Most assistants ask you to approve these calls. | | ๐Ÿ” Idempotent | Calling it again with the same arguments has no further effect. | A tool that mirrors a Public API endpoint links to that endpoint's page. MCP-only tools have no Public API equivalent. version: 1.0.0 servers: - url: https://setup.zuddl.com/api/mcp description: Zuddl MCP server security: - oauth: [] tags: - name: Events - name: Attendees - name: Sessions - name: Speakers - name: Sponsors - name: Locations - name: Teams - name: Brand Kits - name: Registration flows & tickets - name: Analytics paths: /tools/v1_update_sponsor: post: tags: - Sponsors summary: Update Sponsor description: >- **Tool name:** `v1_update_sponsor` ยท **Behaviour:** โœ๏ธ Write ยท ๐Ÿ” Idempotent Change the details of a sponsor on an event in your Zuddl organization. Send only the fields you want to change; anything you omit keeps its current value. Social links you supply are merged by type โ€” a link you name is replaced, a link sent as an empty string is removed, and one you omit is left alone โ€” while the sponsor's tier, booth, assigned tasks and uploaded files keep their current values. On events with the exhibitor portal the attached booth's name and description are derived from the sponsor, so changing the name or tagline re-derives them. Images are not settable here โ€” use v1_upload_sponsor_image. Returns the updated sponsor. **Same as Public API:** [Update a sponsor](/api-reference/sponsors/update-a-sponsor) (`PATCH /v1/events/{eventId}/sponsors/{sponsorId}`) operationId: v1_update_sponsor requestBody: description: The tool's `arguments`, as sent in a JSON-RPC `tools/call` request. content: application/json: schema: type: object properties: eventId: type: string description: Unique identifier of the event sponsorId: type: string description: Unique identifier of the sponsor request: type: object description: >- The fields to change. Every field is optional and anything you omit keeps its current value. properties: contactEmail: type: string description: >- Email address attendees can contact the sponsor on โ€” the setup app labels this field "Contact us email". At most 100 characters. Omit to leave unchanged. description: type: string description: >- Sponsor description; rich-text HTML accepted. At most 3000 characters. Omit to leave unchanged. name: type: string description: >- Sponsor's name. At most 50 characters, and not blank when supplied. Omit to leave unchanged. socialLinks: allOf: - type: object description: Social and website links properties: facebookProfile: type: string description: Facebook profile URL. At most 200 characters. linkedInProfile: type: string description: LinkedIn profile URL. At most 200 characters. twitterProfile: type: string description: Twitter/X profile URL. At most 200 characters. websiteUrl: type: string description: Website URL. At most 200 characters. - description: >- The sponsor's social and website links. Links merge by type: a link you name is replaced, a link sent as an empty string is removed, and one you omit is left as it was. Omit the whole object to leave every link untouched. tagline: type: string description: >- Short tagline shown under the sponsor's name โ€” the setup app labels this field "Tagline". At most 50 characters. Omit to leave unchanged. required: - eventId - request - sponsorId required: true responses: '200': description: A JSON-RPC `tools/call` result. The tool's output is in `content`. components: securitySchemes: oauth: type: http description: >- OAuth 2.1 access token. MCP clients obtain it themselves (dynamic client registration + PKCE) when you connect them to the server URL above. scheme: bearer ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.